Fix login form not having padding on mobile

[xavier-lc]

Fixes DOTCOM-13807

Proposed Changes

• Bring back the side padding to the login form for mobile apps.

Why are these changes being made?

• The changes on Mobile apps: Clear noise on OAuth2 login page #104582 unexpectedly removed the padding

Testing Instructions

• Open the live preview
• Open dev tools, enable responsive view
• Go to /log-in?client_id=2697&redirect_to=https%3A%2F%2Fpublic-api.wordpress.com%2Foauth2%2Fauthorize%3Fclient_id%3D2697%26redirect_uri%3Dwordpress%253A%252F%252Fwpcom-authorize%26response_type%3Dcode%26scope%3Dglobal%26from-calypso%3D1 (the link you would get if trying to log in on the wordpress mobile app for android)
• Check that the header and footer links, terms of service text, and the Back button have been removed.
• Repeat with /log-in?client_id=11&redirect_to=https%3A%2F%2Fpublic-api.wordpress.com%2Foauth2%2Fauthorize%3Fclient_id%3D11%26redirect_uri%3Dwordpress%253A%252F%252Fwpcom-authorize%26response_type%3Dcode%26scope%3Dglobal%26from-calypso%3D1 (the link you would get if trying to log in on the wordpress mobile app for iOs)

Before	After

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-149810

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-149810&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-149810&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~17 bytes added 📈 [gzipped])

name                   parsed_size           gzip_size
entry-reauth-required        +34 B  (+0.0%)      +17 B  (+0.0%)
entry-main                   +34 B  (+0.0%)      +17 B  (+0.0%)
entry-login                  +34 B  (+0.0%)      +17 B  (+0.0%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[mmtr]

Tests well!

[dsas]

This change does what it says, but it looks like other pages have a similar issue, here's the "Lost your password" screen:

[xavier-lc]

This change does what it says, but it looks like other pages have a similar issue, here's the "Lost your password" screen:

Good catch, I've addressed it as well.

[BogdanUngureanu]

Tests well for me (including lost password page)!