Refactor names of parameters of Demand Resolution Strategy

[milstan]

Currently the Demand Resolution Strategy schema of the PCE API uses a different vocabulary than the rest of the components.

For consistency, I suggest:

• renaming those parameters to clearly mirror the exact PRIV terms associated with Demand Actions (e.g. instead of consents call it revoke-consent
• allowing to set automatic/non automatic processing for OBJECT and RESTRICT

Also the documentation is rather limited, i.e. we must say what are other allowed values - how to set non-automatic processing of certain requests. Places this change should affect:

• [ ] swagger
• [ ] blindnet.dev

[m4rk055]

consents is a catch-all category for all revoke-consent, object and restrict. Should we have settings for all 3 separately?

[milstan]

I think it is more intutitive to have 1:1 between ACTION values and this schema here. The users of our system MUST learn about types of demands (i.e. ACTIONs) so we can safely assume they know them. the catch-all term consents introduce an additional concept to learn, which we want to reduce to the minimum.