Invalidate ES cache when projects or groups are transferred

What does this MR do?

Related to #214749 (closed)

• Add a new Elasticsearch cache method to allow for invalidating the cache for a specific type and record id (supports namespace and project)
• Invalidate the cache for a specific project when a project transferred and the following conditions are met:
  • the new namespace has different Elasticsearch settings than the old namespace
• Invalidate the cache for associated projects when a group is transferred and the following conditions are met:
  • elasticsearch_limit_indexing? is enabled
  • the new namespace has Elasticsearch enabled
• Kick off indexing if the project should be indexed after transfer
• Update specs

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team