fix: few changes on zod schemas for compatibility with jsonschema parsers

[zannis]

No description provided.

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[cesarenaldi]

We could call this union out into definitions so to have a nice rust type name generated out of it (e.g., EventLocation).

// shared from other schemas

enum EncryptableUri {
   ...
}

enum EncryptableString {
  // ...
}


// specific to this schema for now as used only here (I believe)
enum EventLocation {
  EncryptableUri(EncryptableUri),
  EncryptableString(EncryptableString)
}

or we can even massage this further so that generated type is 'more flat':

enum EventLocation {
  Uri(URI), /// would be nice to make to our repo types URI, is it possible?
  String(String),
  EcnryptedString(EcnryptedString),
}

[zannis]

the issue with this one is we cannot reliably distinguish between string and encryptedstring without knowledge of the context