chore(many): add tech debt tickets and remove unnecessary todos

[averyjohnston]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Some docs updates need to be made in the ionic-docs repo, in a separate PR. See the contributing guide for details.
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the new behavior?

• Removes a bunch of TODOs that were added a long time ago, don't seem necessary anymore, and/or have no context. Some are also likely to be handled in other tickets, such as notes to add types when we have FW-2690.
• Adds tech debt tickets to TODOs that were missing them and seem useful to keep around.

Let me know if any of these should be kept and if you have context I could add when creating a ticket.

Does this introduce a breaking change?

• Yes
• No

Other information

[liamdebeasi]

One question otherwise this looks good. Thanks for doing this!