Remove old Advanced Search migrations

What does this MR do?

This change consists of 3 MRs:

• (this one) !63001 (merged)
• !63020 (merged)
• !63021 (merged)

This MR does multiple things:

• Adds Elastic::MigrationObsolete as a way to deprecate Advanced Search migrations
• Changes the set_elasticsearch_migration_to method to raise an exception if the migration is not found or it's obsolete
• Deprecates the ApplyMaxAnalyzedOffset migration
• Changes the documentation section Deleting Advanced Search migrations in a major version upgrade in order to reflect the changes in this MR

#323310 (closed)

Rollout plan

1. Get approvals on all MRs (this MR, !63020 (merged), and !63021 (merged))
2. Merge !63021 (merged) into !63020 (merged)
3. Merge !63020 (merged) into this MR
4. Merge this MR into master

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• I have included a changelog entry, or it's not needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• [-] I have tested this MR in all supported browsers, or it's not needed.
• [-] I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• [-] 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

Closes #323310 (closed)