move scopes into root object

docs/developer/decision-records/2024-07-03-additional-catalogrequest-param/README.md

@@ -23,8 +23,7 @@ constraint on them, which makes them "invisible" unless a certain credential is
 
 ## Approach
 
-The `CatalogRequest` will receive a new field `parameters`, which is an extensible map. This map may contain an
-entry `additionalScopes` which is a list of scope strings (as
+The `CatalogRequest` will receive a new nullable field `additionalScopes` which is a list of scope strings (as
 per [DCP Specification, Section 3.1](https://github.com/eclipse-tractusx/identity-trust/blob/main/specifications/verifiable.presentation.protocol.md#31-access-scopes)):
 
 ```json
@@ -36,18 +35,16 @@ per [DCP Specification, Section 3.1](https://github.com/eclipse-tractusx/identit
  "querySpec": {
  //...
  },
- "parameters": {
- "additionalScopes": [
- "org.eclipse.edc.vc.type.AdditionalCredentialType1:read",
- "org.eclipse.edc.vc.type.AdditionalCredentialType2:*"
- ]
- }
+ "additionalScopes": [
+ "org.eclipse.edc.vc.type.AdditionalCredentialType1:read",
+ "org.eclipse.edc.vc.type.AdditionalCredentialType2:*"
+ ]
 }
 ```
 
 Scope strings provided in that fashion will get added to the default scopes.
 
-NB: both the `parameters` map and the `additionalScopes` entry are _OPTIONAL_.
+NB: the `additionalScopes` entry is _OPTIONAL_.
 
 This feature will be added in an Alpha version of the Management API first, specifically of `3.1.0-alpha`. The
 respective URL path will be `/v3.1alpha/api/management/catalog/request` as per