defs-zos: [Fix] prevent schema parsers from hitting recursion-loop while resolving types.

[flouthoc]

Hi Team,

Following PR makes sure that des-zos.json is consistent with schema definition w.r.t to entire spec.

I think following PR ( #1095 ) has introduced type-resolution issues on downstream parsers.
Specifying definition-files for types present in existing .json would result in infinite type resolution loop. However existing convention is just using # instead of specifying def-file for example https://github.com/opencontainers/runtime-spec/blob/master/schema/defs-linux.json

Thanks

[giuseppe]

@najohnsn could you please take a look?

[flouthoc]

Hi @najohnsn Were you able to take a look at this.

[najohnsn]

Sorry, I was on vacation. This looks good to me. Not sure why a relative reference wasn't used before.
@SteeleDesmond, you should take a look too.

[tianon]

This seems like it's doing the opposite of what https://github.com/opencontainers/runtime-spec/blob/82ab996a5bf91804a440391bff43140b17bbadd4/schema/config-linux.json does? (lots of "$ref": "defs-linux.json#/... in there)

[najohnsn]

@tianon, yes, config-linux.json has references to defs-linux.json. But defs-linux.json has the relative reference that is being proposed here for defs-zos.json.

[tianon]

🤦 doh, thanks for clarifying 👍

[giuseppe]

LGTM