added config template that OBI accepts

[itsCheithanya]

Checklist

Fixes #973

• If this enhances / fixes / changes a core feature, I have updated the features documentation

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: itsCheithanya / name: Cheithanya (7e840fb)

[NimrodAvni78]

@itsCheithanya was this written by you or generated automatically?
if not is it something we can generate from a go struct?
because we will need to remember to update this or we will drift from the actual config structure

[itsCheithanya]

@NimrodAvni78 I created this by referencing all the structs ,yes we should keep that in mind if any structs change we need to update here maybe give a NOTE in the structs will be a good approach?

[MrAlias]

I would rather we use something like jsonschema or cue to validate our configuration syntax instead of adding the noise of a one-off yaml file.

[itsCheithanya]

@MrAlias Thanks for the feedback! I understand the concern about maintaining a one-off YAML file. I can refactor this to use either approach . Which would be better? also should I keep this template as documentation alongside the schema,or replace it entirely?

[MrAlias]

@itsCheithanya I would suggest jsonschema as that is used in other parts of OTel including the declarative config.

I would focus on just using jsonschema, no need for this yaml file.

[NimrodAvni78]

ive created a PR that generates json schema automatically from the config struct
#1017

[MrAlias]

Closing in favor of #1017