[WD-5931] rebrand /thank-you page

[akbarkz]

Done

Refresh /thank-you page according to design and copy doc.

QA

• Check out this feature branch
• Run the site using the command ./run serve
• View the site locally in your web browser at: http://0.0.0.0:8027/
• Run through the following QA steps
• Navigate to /thank-you page and check if it's implemented correctly according to the design and copy doc on all screen sizes.

Issue / Card

Fixes https://warthogs.atlassian.net/browse/WD-5931

[webteam-app]

Demo starting at https://microk8s-io-633.demos.haus/thank-you

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (a72c58d) 83.78% compared to head (b9ee7b2) 83.78%. Report is 1 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #633 +/- ## ======================================= Coverage 83.78% 83.78% ======================================= Files 2 2 Lines 74 74 ======================================= Hits 62 62 Misses 12 12 ``` | [Flag](https://app.codecov.io/gh/canonical/microk8s.io/pull/633/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=canonical) | Coverage Δ | | |---|---|---| | [python](https://app.codecov.io/gh/canonical/microk8s.io/pull/633/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=canonical) | `83.78% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=canonical#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[lyubomir-popov]

Looks good, just a couple of small things:

• Spacing in the header isn't quite right - we need .p-strip.is-shallow.u-no-padding--bottom>.p-section, not .p-strip deep following a shallow section as we have heree. a good example is the data overview page: https://canonical.com/data

• u-no-margin--bottom on the h1 please

• • p-rule class on all <hr>s

[akbarkz]

@lyubomir-popov addressed your comments, ptal