Taxonomy term ID from URL ViewsArgumentDefault plugin does not apply node cache tags when "Load filter from node page" is selected

Problem/Motivation

#3427374: taxonomy_tid ViewsArgumentDefault plugin doesn't add cache tags was committed in attempt to fix an issue where when "Load default filter from node page, that's good for related taxonomy blocks" is used the view does not include any cache metadata from the node being viewed, resulting in stale data displayed after updates.

As mentioned in https://www.drupal.org/project/drupal/issues/3427374#comment-15645693 this fix does nothing and the issue persists. Opening this as a new issue given the time that has passed since that was closed.

Cache metadata is collected from the handlers when the view is saved (https://git.drupalcode.org/project/drupal/-/blob/11.2.8/core/modules/vie...) - cache metadata is not collected at runtime from the argument / handler.

#3091671: Validate user has access option in contextual filter does not bubble access cacheability for views page is a similar issue - where cache metadata from the argument validator doesn't bubble up.

Together - both issues suggest we need a better way to apply cache metadata at run time from various views plugins. Or a clarified process to do this properly.

From that related issue @danflanagan8 identified an existing issue #2853592: Cacheability metadata can't be set from within argument default handlers. and test / test plugin in core that implies a supported way to do this is to apply cache data to the view element itself.

Steps to reproduce

Using the standard profile:

• Create a new view block display of taxonomy terms, add a contextual filter for "Taxonomy term: Term ID"
• Select "Provide default value" for "When the filter value is NOT available"
• Select "Taxonomy term ID from URL"
• Select "Load default filter from node page, that's good for related taxonomy blocks"
• Place the block for article content type
• Add an article with tags, observe the view is present
• Edit the article, observe the view is present with the old data

Proposed resolution

Head in same direction as #3091671: Validate user has access option in contextual filter does not bubble access cacheability for views page - apply the cache metadata to the view element itself when the default value is loaded - unless there is a better way to do this.

Remaining tasks

• Revert 3427374
• Add a test using an actual view, test was flawed in 3427374 so we potentially need to verify via a functional test here?
• Fix cache metadata
• Review

User interface changes

n/a

Introduced terminology

n/a

API changes

n/a

Data model changes

n/a

Release notes snippet