Add mock definitions for SSO Server Definitions

[andy-maier]

We have recently added support for SSO server definitions including mock support.

This ticket is for adding at least one SSO server definition object to the mock yaml files. Since SSO Server Definition support was added in z17, this requires first to copy the mock yaml file for z16 to z17, and then add it only in the file for z17.

[passionworkeer]

I’d treat this mainly as a fixture-versioning task: copy the z16 mock YAML to z17 first, then add exactly one minimal SSO server definition only in z17 so older mock generations stay untouched. A good test shape would be: verify the object is discoverable on z17, verify its read path works, and verify z16 still behaves as ‘feature unavailable’. If the definition includes write-only fields like client-secret, it would also be useful to align the fixture with the masking/filtering expectations from the mock-property issue so future tests don’t encode the wrong behavior.

[andy-maier]

@passionworkeer Thanks for this input. I agree. If you want to provide a PR for it, go for it! (and let me know so I can update the assignee :-)

Note issue #2122 about support for write-only properties. I'm currently working on that.