[Meta] JSON:API 1.1 spec compliance/support

Problem/Motivation

This issue tracks child issues relating to JSON:API 1.1 spec compliance. The announced tag date for 1.1 is September 30, 2022.

Reference: Changelist

Remaining tasks

Areas where Drupal is not 1.0 compliant but we were ahead of 1.1; ensure tagged spec compliance.

• #3279366: [PP-1] Implement json:api 1.1 server-required profile error handling/signaling
• #3279364: [PP-1] JSON:API 1.1 Implement `error.source.missing.key` data to compliment `error.source.pointer`

Areas where Drupal is incompatible and there is no existing PP on JSON:API 1.1; that is, we're just plain out of spec.

New features/options in 1.1 that Drupal can support

• #2955020: Spec Compliance: JSON API's profile/extention (Fancy Filters, Drupal sorting, Drupal pagination, relationship arity) needs to be explicitly communicated

Overview of all changes in spec and their releated issues:

Spec changelist

1. #3386046: JSON:API 1.1: "@-Members"
2. error object type links.
1. #3279364: [PP-1] JSON:API 1.1 Implement `error.source.missing.key` data to compliment `error.source.pointer`
3. Recommending camelCased
4. Extensions #2955020: Spec Compliance: JSON API's profile/extention (Fancy Filters, Drupal sorting, Drupal pagination, relationship arity) needs to be explicitly communicated
5. Profiles #2955020: Spec Compliance: JSON API's profile/extention (Fancy Filters, Drupal sorting, Drupal pagination, relationship arity) needs to be explicitly communicated
6. Links can be represented as RFC 8288-style web links.
7. describedby links member was added #3386063: JSON:API 1.1: Add descibeBy API to add link to top level, resource and relationship objects
8. Local IDs were introduced so that a client can create a relationship to a resource yet-to-be created by the same request. I don't think we need to do this, we dont really allow creating multple resource in one request.
9. The link object params member was removed
10. The link object anchor target attribute was removed
11. Clarified details regarding expected and allowed responses, query parameters, and more.

Changelog for releases after 1.0

RC 1

• New features include: profiles, ”@-Members”, and error object type links.
• There are editorial clarifications around: query parameters (their parsing/serialization, and reserved parameter names), the appropriate status code for specific responses, and the presence of the included key even when its value is an empty array.
• JSON:API switched to recommending camelCased names.

RC 2

• Extensions were added and the scope of profiles were reduced since their introduction in RC1.
• Links can be represented as RFC 8288-style web links.
• A new describedby links member was added so that implementors can incorporate description documents (e.g. OpenAPI or JSON Schema) directly into their APIs.
• Local IDs were introduced so that a client can create a relationship to a resource yet-to-be created by the same request.

RC 3

• Refined links objects. The link object params member was removed to better align with other JSON link serializations. The anchor target attribute was also removed. It may be restored in a future minor release.

RC 4

• Formalized the definition of specification and implementation semantics.
• Refined the definitions of extensions and profiles.
• Clarified details regarding expected and allowed responses, query parameters, and more.