FieldResolver::resolveInternalIncludePath is very slow with complex and nested includes

Here is a starter on an approach for the persistent cache. It caches based on the resource type and include path (parts, concatenated and hashed).

Based on the performance testing below, there is definitely potential with warm caches, but a hit with cold caches.

Some initial local performance test (with memcache as the default backend):

Baseline: 325ms

Patch as is:
- With cold caches: 1,530ms
- With warm caches: 137ms

Using cache.jsonapi_resource_types (chained memory & default):
- With cold caches: 1,100ms
- With warm caches: 146ms

As above but with the database as the default backend:

Baseline: 340ms

Patch as is:
- With cold caches: 2,460ms
- With warm caches: 175ms

Using cache.jsonapi_resource_types (chained memory & default):
- With cold caches: 2,550ms
- With warm caches: 177ms

Rerolled the patch for 11.x.