Use indirect parametrization between version oracle token and validator

[jstolarek]

We have the following two requirements:

1. Version oracle tokens should only be minted if they are sent to version oracle validator. (Exception: initial mint during genesis.)
2. Version oracle validator should only allow operations on UTxOs containing version oracle tokens

This introduces a circular dependency, where the validator needs to know the token minting policy (currency symbol) and the token minting policy needs to know the validator address.

Currently existing scripts ignore the first requirement and don't check the destination address during minting. We should fix this by introducing an indirect parametrization as described in this comment.

Note that if we implement SIP-14 and the solution ends up having dedicated scripts for minting data oracle tokens and data oracle validator we will have to use the same indirect parametrization mechanism.

---

IOG Jira: https://input-output.atlassian.net/browse/ETCM-6049

[jstolarek]

@jankun4 do I understand correctly that we have implemented an alternative design and this can be closed?