2891/add sign up to beginning of application flow

[KrissDrawing]

Pull Request Template

Issue Overview

This PR addresses #issue

• This change addresses the issue in full
• This change addresses only certain aspects of the issue
• This change is a dependency for another issue
• This change has a dependency from another issue

Description

Main scope of task was to add create account panel to start of application flow. I used for that ActionBlock component. To unify both login and create account panels, changed login to also use ActionBlock.
Updated also change your language to match designs recommendations.

Using background as string in ActionBlock generates warnings because we're using enums in it. That's the way they're implemented in storybook so i followed the pattern. Let me know if i should use enums there.

How Can This Be Tested/Reviewed?

Start new application being logged out (f.e. http://localhost:3000/applications/start/choose-language?listingId=fba78bf7-24cb-460a-8c6c-8caf6b1d1b42). Check again after log in.

Test goes to application, press the create-account button and checks if we redirected to /create-account

Checklist:

• My code follows the style guidelines of this project
• I have added QA notes to the issue with applicable URLs
• I have performed a self-review of my own code
• I have reviewed the changes in a desktop view
• I have reviewed the changes in a mobile view
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have assigned reviewers
• I have run yarn generate:client and/or created a migration if I made backend changes that require them
• I have exported any new pieces added to ui-components
• My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
• Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:

Steps to review a PR:

• Read and understand the issue, and ensure the author has added QA notes
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
• Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:

If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

[netlify]

✅ Deploy Preview for dev-bloom ready!

Name	Link
🔨 Latest commit	cc1fb53
🔍 Latest deploy log	https://app.netlify.com/sites/dev-bloom/deploys/630e25d384d69c0009355130
😎 Deploy Preview	https://deploy-preview-3018--dev-bloom.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

✅ Deploy Preview for dev-partners-bloom ready!

Name	Link
🔨 Latest commit	cc1fb53
🔍 Latest deploy log	https://app.netlify.com/sites/dev-partners-bloom/deploys/630e25d39ad5f0000adc0af5
😎 Deploy Preview	https://deploy-preview-3018--dev-partners-bloom.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

✅ Deploy Preview for dev-storybook-bloom ready!

Name	Link
🔨 Latest commit	cc1fb53
🔍 Latest deploy log	https://app.netlify.com/sites/dev-storybook-bloom/deploys/630e25d3c936860008b79b66
😎 Deploy Preview	https://deploy-preview-3018--dev-storybook-bloom.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[ludtkemorgan]

Looks good!

[emilyjablonski]

This is looking great! I just have one note - thank you for writing a test ✨ - but we should remove it. We might be starting to shift our testing strategy a little to lean less on Cypress for smaller test cases. We don't have unit tests set up for the public site yet, so we couldn't yet shift this to a unit test which would be ideal, so in the meantime I'd recommend removing the Cypress test just so that we don't add onto our Cypress suite which is more resource-intensive at the moment. This is definitely new, so sorry for missing context!