global: view configuration refactoring

[lnielsen]

Currently Records-REST can be configured with using the RECORDS_REST_ENDPOINTS variable with takes a long list of arguments.

Problem:

We are adding more and more options to the list of configuration variables. Each time an option is added, it needs to be propagated down through views. This causes quite a lot of boiler plate code, and possibilities for improper configuration.

Also, it is hard to reuse and repurpose the Records REST API for e.g. the deposit API.

Proposal:

1. Wrap all configuration options in an object, so that just one object is passed around
2. Create a endpoint context for each request, so it's easier to override behaviour in e.g. deposit.

Co-authored-by: @jirikuncar

[hachreak]

IMHO maybe invenio-records-rest can be simplified moving:

• the rest-specific code as this inside invenio-rest.
• refactor the records rest specific code like a series of utilities ready-to-use.

Then, avoid a single point of configuration like create_blueprint() to permit to the single implementation like deposit to:

• quickly implement its views because most of the code is already done
• applying the behavior that it prefers because it has the full control of the request flow (like which error codes returns or the endpoint names)
• cutting out the functionalities and configurations that it doesn't need.