Spike: Figure out where we want to require analytics

[timwright12]

Description

There are a couple types of basic analytics collection in the app: screen views and click events. This ticket is to inventory any UI patterns we feel always need to be tracked (like screen views and clicks/taps). The output of the ticket should be more tickets with specific components inside that app that should have analytics as a pre-built requirement. For example, anytime someone creates a new screen it comes with automatic analytics (same with buttons or links).

The goals are two part

• Make sure default analytics are always available when new features are built
• Reduce the load of engineering reviewing PRs making sure all required analytics are in place

Acceptance Criteria

• [ ] UI patterns in the app that require analytics are documented (on the docs site)
• [ ] New tickets are created to update app components (not design system components) to have automatic analytics

[timwright12]

@DonMcCaugheyUSDS @Hallm13 Spike ticket from yesterday's analytics meeting

@ajsarkar28 @OVezeamama Just added the two of you as primary assignees for this ticket since I'm not sure if we actually need engineering to do anything here outside of a consult or maybe helping write ticket content. Feel free to reassign though.