Drop clusters_applications_ingress table

We're cleaning up the deprecated Clusters::Applications code related to Remove clusters_applications_* code (#366573 - closed)

Application code that used this table was removed in Clusters::Applications models removal (#388696 - closed)

In !117460 (merged) we dropped the foreign keys. This was in post deploy migration that has been run.

This MR's purpose is to

• drop the clusters_applications_ingress table
• move the dictionary files per these instructions

For transparency, this was originally part of a single MR that drops many clusters_applications* tables, but sensing some concern around this I have split them into individual MRs.

Table usage

Thanos Query showing table usage. It's non-zero but very tiny. I don't think it represents application usage with it being this small but would love a Database reviewer's insight on this.

Migration output

main: == [advisory_lock_connection] object_id: 275100, pg_backend_pid: 75326
main: == 20230502201251 DropClustersApplicationsIngress: migrating ==================
main: -- drop_table(:clusters_applications_ingress)
main:    -> 0.0023s
main: == 20230502201251 DropClustersApplicationsIngress: migrated (0.0063s) =========

main: == [advisory_lock_connection] object_id: 275100, pg_backend_pid: 75326
ci: == [advisory_lock_connection] object_id: 275280, pg_backend_pid: 75328
ci: == 20230502201251 DropClustersApplicationsIngress: migrating ==================
ci: -- drop_table(:clusters_applications_ingress)
ci:    -> 0.0011s
ci: == 20230502201251 DropClustersApplicationsIngress: migrated (0.0091s) =========

ci: == [advisory_lock_connection] object_id: 275280, pg_backend_pid: 75328