Cleanup ArchiveRevokedAccessTokens background migration

What does this MR do and why?

Cleanup ArchiveRevokedAccessTokens Batched Background Migration

Remove code for the finalized ArchiveRevokedAccessTokens batched background migration following the standard cleanup process.

• Add cleanup migration to delete migration record from database
• Remove background migration class and spec
• Remove queue migration spec
• Remove migration documentation

The migration was finalized in 18.6 and is now safe to clean up.

Related: #562373

Additional notes

• Migration was enqueued in 18.5: !197692 (merged)
  • The migration only targeted gitlab.com. This migration did not target self-managed instances.
• Finalized in 18.6: !211207 (merged)
  • Can verify it is finalized with /chatops run batched_background_migrations status 2001059 --database main
• Since we only targeted .com, there is no need to wait until next required stop to delete the migration, per this conversation

References

• Issue: #562373
• https://docs.gitlab.com/development/database/batched_background_migrations/#deleting-batched-background-migration-code
• BBM introduced and enqueued in: !197692 (merged)
• BBM finalized in: !211207 (merged)

Screenshots or screen recordings

Before	After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.