Removing unused database tables and references to them

[ckd002]

Description

This PR removes a number of tables that are not currently used in EDPUB. It also removes any references to those tables that may be lingering in queries and templates.

Linked JIRA Task or Github Issue

JIRA Task: EDPUB-1624

Types of changes

What types of changes does your code introduce to Earthdata Pub (EDPub)?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if adding or updating the existing documentation resources)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the Contributing Guide
• I have updated the CHANGELOG
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Validation Steps

This will help us get a jump start on validating your PR by describing the steps to replicate
and validate the expected behavior. (For an example of good validation instructions, check out Bryan's Bouncy Ball PR.)

1. Deploy previous version of the API locally
2. Make sure all merge request checks have passed (CI/CD).
3. Pull related branches locally.
4. Run the update commands from the update file
5. Verify that the following tables have been removed sucessfully

• edpgroup_parent
• edpgroup_permission_submission
• edpgroup_subscription_action
• edpgroup_subscription_daac
• edpgroup_subscription_form
• edpgroup_subscription_service
• edpgroup_subscription_submission
• edpgroup_subscription_workflow
• edpuser_permission_submission
• edpuser_subscription_action esa
• edpuser_subscription_form
• edpuser_subscription_service
• edpuser_subscription_submission
• edpuser_subscription_workflow
• module
• submission_lock

6. Navigate to the Groups page
7. Select a group
8. Verify that the information displays as expected
9. Navigate to the Users page
10. Select a user
11. Verify that the information displays as expected
12. Re-deploy the API ensuring the new branch is being used
13. Verify that the tables listed in step 5 are never created.

Further comments