Ask VA/ 1475 update require sign in logic

[ediiotero]

Are you removing, renaming or moving a folder in this PR?

• No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
• Yes, I'm removing, renaming or moving a folder

Did you change site-wide styles, platform utilities or other infrastructure?

• No
• Yes, and I used the proxy-rewrite steps to test the injected header scenario

Summary

• Require user to sign in if question is about myself or someone else
• (If bug, how to reproduce)
• (What is the solution, why is this the solution)
• Ask VA team owns the form
• (If using a flipper, what is the end date of the flipper being required/success criteria being targeted)

Related issue(s)

• Ticket: 1475

Testing done

• Modal will tell user to sign in if the question is about Myself or Someone else
• Describe the steps required to verify your changes are working as expected
• Manual testing

Screenshots

UI did not change

What areas of the site does it impact?

Only impacts the Ask VA form.

Acceptance criteria

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user

[hemeshvpatel]

Lgtm!

[harshil1793]

It looks like the new code at line 10, 19, 93, and 95 introduces a slew of new linting warnings. Can we please clean those up before we merge this?