THEMES-760: Identity Blocks | Login links block

[vgalatro]

Description

This PR adds in the Login links block that accompanies the sign up and log in forms. It also corrects some styling issues with the single column layout related to the display of these blocks.

Jira Ticket

• THEMES-760

Acceptance Criteria

Login links block is converted to v2.

Test Steps

1. Checkout this branch git checkout THEMES-760
2. Run fusion repo with linked blocks npx fusion start -f -l @wpmedia/identity-block,@wpmedia/single-column-layout-block
3. Create a page using the single column layout.
4. Add the Identity Log In - Arc Block and the Identity Login Links - Arc Block to the "body" section of the page.
5. In the Identity Login Links - Arc Block make sure "Show Forgot Password link" and "Show Sign up link" are checked. You can customized the URLs for each as well.
6. Make sure the login links appear below the form as seen on the designs (https://www.figma.com/file/vWVGgZfZVBdSX7ACo3kmjr/Enhanced-Styling-Design-System?type=design&node-id=12874-178005&mode=design&t=JptOC1IZ0G9wCmAD-4).
7. Now replace Identity Log In - Arc Block with Identity Sign Up - Arc Block.
8. In the Identity Login Links - Arc Block make sure "Show Login link" is checked. You can customized the URL as well.
9. Make sure the login link appear below the form as seen on the designs (https://www.figma.com/file/vWVGgZfZVBdSX7ACo3kmjr/Enhanced-Styling-Design-System?type=design&node-id=8411-119293&mode=design&t=BeXCdtxm1ekWDLRJ-4).

Author Checklist

• Confirmed all the test steps a reviewer will follow above are working.
• Confirmed there are no linter errors. Please run npm run lint to check for errors. Often, npm run lint:fix will fix those errors and warnings.
• Ran this code locally and checked that there are not any unintended side effects. For example, that a CSS selector is scoped only to a particular block.
• Confirmed this PR has reasonable code coverage. You can run npm run test:coverage to see your progress.
  • Confirmed this PR has unit test files
  • Ran npm run test, made sure all tests are passing
  • If the amount of work to write unit tests for this change are excessive,
    please explain why (so that we can fix it whenever it gets refactored).
• Confirmed relevant documentation has been updated/added.

Reviewer Checklist

The reviewer of the PR should copy-paste this template into the review comments on review.

• Linting code actions have passed.
• Ran the code locally based on the test instructions.
  • I don’t think this is needed to be tested locally. For example, a padding style change (storybook?) or a logic change (write a test).
• I am a member of the engine theme team so that I can approve and merge this. If you're not on the team, you won't have access to approve and merge this pr.
• Looked to see that the new or changed code has code coverage, specifically. We want the global code coverage to keep on going up with targeted testing.