Partner Portal: Add a Terms of Service consent gate to access the portal

[atanas-dev]

Context: p1616184557016100-slack-CQN0YDYM7

Changes proposed in this Pull Request

• Add a Terms of Service consent gate to access the Partner Portal.

Testing instructions

• If you do not have a partner key, please contact Infinity for one or you will be unable to view test this PR.
• Check out this PR locally, then run yarn && yarn start-jetpack-cloud.

Case 1: You don't have a partner or at least 1 active partner key.

• Visit http://jetpack.cloud.localhost:3000/partner-portal
• You should be redirected to /partner-portal/partner which should show an error message like so:
  

Case 2: You have an active partner key but you have not accepted the new ToS.

• Visit http://jetpack.cloud.localhost:3000/partner-portal
• You should be redirected to /partner-portal/terms-of-service:
  
• Accepting the terms should redirect you to key selection if you have multiple keys or to your license listing if you only have a single key.

Case 3: You have an active partner key and you have already accepted the new ToS once.

• Visit http://jetpack.cloud.localhost:3000/partner-portal
• You should be redirected to key selection if you have multiple keys or to your license listing if you only have a single key, skipping the ToS step.

[matticbot]

Test live: https://calypso.live/?branch=add/partner-portal-tos-gate

[matticbot]

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

Sections (~849 bytes added 📈 [gzipped])

name                          parsed_size           gzip_size
jetpack-cloud-partner-portal      +3805 B  (+3.4%)     +849 B  (+2.5%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Async-loaded Components (~288 bytes added 📈 [gzipped])

name                                              parsed_size           gzip_size
async-load-calypso-components-jetpack-portal-nav       +951 B  (+3.7%)     +288 B  (+3.7%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

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.

[IanRamosC]

The functionality tests well. Besides the blockers, I would only ping @keoshi to check the UI before releasing it.

[keoshi]

This looks good to me so far. Would like to see what the rest of the UI looks like... Are we showing menus when the TOS is display? I don't think we should show anything until the TOS are accepted, right?

I can also spin the PR later today and test it for myself, but that would be my only concern for now.

Finally, just said this to @atanas-dev but will say it again — apologies for not having replied here sooner. I got the email ping but it's been sitting on my todo list because I'm extra busy lately.

[IanRamosC]

Looks good!

[a8ci18n]

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/5702430

Thank you @atanas-dev for including a screenshot in the description! This is really helpful for our translators.

[a8ci18n]

Translation for this Pull Request has now been finished.