[Improvement] flagd json schema files should be namespaced under resources

[Kavindu-Dodan]

Background

flagd provider utilizes schema files to validate flags when working in in-process mode. Currently, these json schema files are copied when building the binary to resources and kept in the root level [1]. And they are named flags.json & targeting.json.

Problem

In an application that uses flagd Java provider for feature flagging, there can be conflicting JSON files with similar names to the above schema files in the classpath. This especially concerns the name flags.json as many flagd examples use flags.json as a flag source file.

Improvement

Given our underlying library (seems to) support namespaced locations [2], we should improve our schema locations with an appropriate namespace to avoid classpath conflicts.

AC

Provider works & validates flags correctly with the namespaced schemas in the classpath.

[1] - https://github.com/open-feature/java-sdk-contrib/blob/dev.openfeature.contrib.providers.flagd-v0.8.3/providers/flagd/pom.xml#L236-L258
[2] - https://github.com/networknt/json-schema-validator/blob/master/doc/schema-retrieval.md#configuring-mappings

[mehtasankets]

@Kavindu-Dodan I can take a stab at this.

Can we finalize on the new namespace locations to use?
I propose classpath:schemas/flagd/{flags|targeting}.json and classpath:/schemas/flagd/inprocess/{flags|targeting}.json

[Kavindu-Dodan]

@mehtasankets

I can take a stab at this

Nice.

Regarding the schema, I think flagd/schemas is better. And then place the json schema files targeting.json & flags.json under that resource directory.

flagd/schemas/flags.json , flagd/schemas/targeting.json

[Kavindu-Dodan]

Assigned the issue to you @mehtasankets . Let me know if you have further doubts

[mehtasankets]

@Kavindu-Dodan for review: #850

[Kavindu-Dodan]

@mehtasankets thanks for the PR. Will include this with the next release :)