fix: support different schema of meta properties

[shrutiburman]

Fixes DII-368

The response meta properties can have two structures, one where the meta tag is present and under those all properties are listed, another where the meta tag isn't there but the properties are present. This PR enables support for different variations of meta properties schema.

Checklist

• [x] I acknowledge that all my contributions will be made under the project's license
• [ ] I have made a material change to the repo (functionality, testing, spelling, grammar)
• [x] I have read the Contribution Guidelines and my PR follows them
• [x] I have titled the PR appropriately
• [x] I have updated my branch with the main branch
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added the necessary documentation about the functionality in the appropriate .md file
• [ ] I have added inline documentation to the code I modified

If you have questions, please file a support ticket, or create a GitHub Issue in this repository.

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

87.5% Coverage
0.0% Duplication

[childish-sambino]

I'm not understanding why this change is needed in the existing code base. This isn't currently causing any problems. Is this a change that should be in oai-generator instead?

[shrutiburman]

This ticket was going to populate meta properties in case the properties are not nested under the tag "meta". Turns out, the current implementation handles this case with "uri" tag, which if present, the meta properties will be built from root nodes. So we are good here, without any modifications.