Simplify social event support in internal landing page

[alexeykazakov]

This PR introduces a few changes to the internal landing page to better support social events:

1. Removes the ToS checkbox. ToS are enforced via SSO anyway. We don't need it here.
2. Add OpenShift AI card and update the card descriptions (the Dev Spaces card is still hidden):
   
3. Hide the token claims & proxy login info under a collapsible +:
   
4. If the verification is required then hide the phone verification field and show the Activation Code field only:
   

[sonarcloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexeykazakov, sbryzak

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [alexeykazakov,sbryzak]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.73%. Comparing base (5faca3a) to head (43c4c3c).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #456   +/-   ##
=======================================
  Coverage   78.73%   78.73%           
=======================================
  Files          42       42           
  Lines        2742     2742           
=======================================
  Hits         2159     2159           
  Misses        490      490           
  Partials       93       93           

Flag	Coverage Δ
unittests	78.73% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[xcoulon]

4. If the verification is required then hide the phone verification field and show the Activation Code field only:

I'm curious, how can we make sure that all hackathon users will have verification required (so they have a chance to input the Activation Code)

[rajivnathan]

I'm curious, how can we make sure that all hackathon users will have verification required (so they have a chance to input the Activation Code)

@xcoulon I think Matous explained it here: https://redhat-internal.slack.com/archives/C07JLT363ME/p1724767269456019?thread_ts=1724748364.070099&cid=C07JLT363ME

[xcoulon]

I'm curious, how can we make sure that all hackathon users will have verification required (so they have a chance to input the Activation Code)

@xcoulon I think Matous explained it here: https://redhat-internal.slack.com/archives/C07JLT363ME/p1724767269456019?thread_ts=1724748364.070099&cid=C07JLT363ME

I believe this was rather a 1-time hack to verify the workflow. But @alexeykazakov mentioned a more permanent solution in Slack