Finalize secondary nav design based on stakeholder feedback

[wesrowe]

Description

User story

As a Cartographers team member, I want to finalize the secondary nav design with buy-in from stakeholders in OCTO and OCC, so that we can move to implementation.

Notes

• split from #74998 in refinement on 2/7; path forward might change again
• OCC timing may change with the slip of the overall schedule
• Address account use cases: do we show it to users who don't have access to tools? (LOA1, not registered)
• Google analytics: figure out how secondary nav events should be captured within the information architecture of GA events. Determine whether we can use an existing pattern or need to request a custom implementation from the Platform Analytics team.
• Datadog RUM: specify "action names" that would enable us to easily find 2N events when building funnels

Possible tasks:

• adapt findings presentation for OCC audience
• a11y review
• analytics: discover how 2N events should fit within the IA of VA's GA
• analytics: how should actions be named in Datadog RUM?

Acceptance criteria

• Presented research findings (adapting presentation as necessary) to OCTO and stakeholders
  • Wed OCC meeting
  • Monday weekly UX meeting (if schedule allows)
• Achieved alignment from necessary stakeholders
• Documented final design in Figma (?), including any needed annotations for UX flow, analytics, and a11y
• Requested analytics implementation from Platform Analytics team if necessary

[wesrowe]

ended up duplicating this in the integration rush. closing.