Checking token module in token hooks is expensive

Yes, token alters in a lot of tokens, to figure out if tokens are defined by itself and not others, it checks that. Otherwise it might also try to act on core tokens such as node:title.

It's already optimized to use a cache collector, this only happens on the first request, afterwards it read from a minimal cache the in the bootstrap bin since the most recent release or so.

❌ Does not fix the issue — applied MR !137, ran ddev drush cr and loaded /node/4 as anonymous with metatag enabled: the call still arrives from TokenTokensHooks.php:651, so TokenModuleProvider::getTokenModule() keeps token info discovery on the critical path of every HTML request after a cache clear.

Notes

• The two checks the MR removes are not the only ones: extending the same reasoning to lines 651, 659, 667, 673 and 679 would take the discovery off the request path entirely, which is what the issue summary aims for.
• If the ownership check has to stay for the entity tokens, the token names token.module claims for entity types are a fixed set, so comparing against a hardcoded list would avoid getTokenInfo() altogether.
• At line 651 the expensive call is also evaluated before the cheap isNew() and hasLinkTemplate() guards; reordering helps when the entity has no canonical link, but not on a node page where [node:url] is requested.

Upload network usage with always cold cache