Invalidate JSON:API Extras' cache tags when needed

Here is the initial patch to start things off - adding the new tags on the repository's list.
This is based off the patch from #31 in the parent issue.

@wim, am I understanding the direction correctly?

#4 :D BIG +1!

How about 7.1, as 7.0 is already EOL...

So we need to clear that cache tags on any modification of resources in jsonapi_extras. The property name needs to change, as it was renamed in the parent issue.

I've done some manual testing and this seems to work correctly with the latest parch from @rhristov.
Does it need something more?

This would be a better fix to acommodate the latest changes in the parent issue.

I can not make a patch as my project is a bit behind on versions.

But the main idea is to drop the property definition we currently have and overwrite the property from the c-tor and compute the property after the parent is constructed.

  /**
   * {@inheritdoc}
   */
  public function __construct(
    EntityTypeManagerInterface $entity_type_manager, 
    EntityTypeBundleInfoInterface $entity_bundle_info, 
    EntityFieldManagerInterface $entity_field_manager, 
    CacheBackendInterface $cache
  ) {
    parent::__construct($entity_type_manager, $entity_bundle_info, $entity_field_manager, $cache);

    $this->cacheTags = array_merge($this->cacheTags, [
      'config:jsonapi_extras.settings',
      'config:jsonapi_resource_config_list',
    ]);
  }

So now that the other one is committed, Are we re-opening this or opening a new one?

Here is a patch for the proposed solution in #19.

Oops missing use statements :D

Added them :)...

Found it :)!

It will work against D8.8, but it's failing against D8.7, as the patch was not committed there yet.
Here is a version with feature detection in place, that will handle the case for both versions of the module, as well as if people decide to patch 8.7 with the latest patch from the parent issue.

Ping.

Ping again :D.

The patch should work. Moving to RTBC.