Layer 2 configuration creation and maintenance

Beckn-ONIX requires layer 2 configuration files to be present for the domain name(field name - domain) and core spec version (field name - version) specified in the message context. These layer 2 configuration currently are all encompassing yaml file with domain specific and network specific rules. The reference Beckn Adapter expects them to be present in its file system with the name `{domain}_{version}.yaml) With regards to this, we have the following issues:
1. We will need a yaml file for each domain name used in the examples we support in sandbox and those that we use in Experience Center.
2. The spec team is publishing 1.1 complaint domain specs. We need to ensure this covers all the examples and EC apps.
3. Currently the domain names are not standardized. e.g in sandbox and EC we use the name desp:courses while in the examples in the repository, we use onest:learning-experiences
4. The domain specs currently only use examples and not any rules. So essentially from a validation perspective, they are identical to core spec. The spec team will gradually be modifying this to make it more featureful.

Towards the above, we need an understanding with the spec team. I am assuming that a few of these will be sorted out.
1. Standardization of domain names for the published examples and EC apps.
2. Ownership of layer 2 configuration files
3. A place to update these files on github, so users of Beckn-ONIX can use that in the download script.