Ran linting, updated to have a single /cleanup endpoint

[jcadam14]

Closes #35

Added the following paths:

/v1/cleanup/{lei} <- All institutions and filings for a LEI
/v1/cleanup/institution/{lei} <- Institutions for a LEI
/v1/cleanup/filing/{lei}/{period_code} <- Filings for a LEI for a given period
/v1/cleanup/submissions/{lei}/{period_code} <- Submissions for a LEI for a given period

Ran linting, so some of the changes are black/ruff adjustments

• Created a cleanup.py Router with a single endpoint for /v1/cleanup/{lei}
• Updated main.py so the app uses the one router currently
• Left the existing code in there, with the previous endpoints, "just in case" we want to include those as separate endpoints to hit. Right now, only the /cleanup one is planned on being used. But @guffee23 / @nargis-sultani can play with adding the other endpoints as additional routers as desired.
• Pulled out code that deletes institutions and filing data to "delete_helper" functions in each of the filing and institution router classes. Made them usable by the /cleanup endpoint as well as the previous separate set of endpoints (again just in case we want all that modularity in there, none of the code was replaced/removed)

[hkeeler]

Overall looks great. Just a couple nitpicks in there.

[hkeeler]

Do you need to catch it if you you're just going to re-raise it?

[jcadam14]

Updated to instead raise the following like we do with our other exceptions, gracefully handling this condition:

            raise RegTechHttpException(
                status_code=HTTPStatus.INTERNAL_SERVER_ERROR,
                name="Delete Filing Server Error",
                detail=f"Server error while trying to delete filing for LEI {lei}.",
            ) from e

[hkeeler]

I'm guessing there are some test scenarios where there won't be email domains...like if you're testing that that user cannot get past that step in the process without those domains. :) It doesn't seem like an error in that case. Maybe a warn?

[hkeeler]

Same.

[jcadam14]

Honestly looking at the repo code for deleting domains and types, I don't know how this code will even be hit. If there isn't a domain or type, the filter will just not do anything, but the return object for delete_domains and delete_sbl_type will always exist. So that logger code wouldn't be hit. If an exception is hit while trying to delete either, it would be thrown up in the response and the logger code wouldn't be hit.

I'm going to write a story for Nargis to rework the code for the repo or this section to properly check if the domains and types exist and log a warning because yeah I think these loggers are unreachable.

[jcadam14]

Created #40 if you want to check if that properly captures the issue here.