Update data guideline: Parameters and parameter object features

This data guideline needs to be updated: https://github.com/mdn/browser-compat-data/blob/main/docs/data-guidelines/README.md#parameters-and-parameter-object-features

See the discussion in https://github.com/mdn/browser-compat-data/pull/29739#issuecomment-4627771274 as well as https://github.com/mdn/browser-compat-data/pull/29451 which used a nested structure.

In today's BCD call, we agreed that nesting structures are better.

• Better validation/linting is in place if features are properly nested.
• MDN rendering for deeply nested features is AFAIK not a problem anymore.

So the guidelines should reflect that and present how to nest parameters keys correctly. It will probably look like this:

• someMethod
  • options_parameter
    • propA
    • propB
    • propC_options_parameter (we don't need the longer names)

We should be using names from the specification (there are different names for the object parameters like "option", "init", "configuration")

Start with docs/data-guidelines/README.md at the “Parameters and parameter object features” section. Read the linked discussion and pull request to understand the agreed nested structure and use specification names for parameter objects. Done means the guideline clearly documents the nested parameter-key pattern and no longer recommends the older structure.