EPMRPP-90473 || Report Launch as Important

[Vadim73i]

PR Checklist

• Have you verified that the PR is pointing to the correct target branch? (develop for features/bugfixes, other if mentioned in the task)
• Have you verified that your branch is consistent with the target branch and has no conflicts? (if not, make a rebase under the target branch)
• Have you checked that everything works within the branch according to the task description and tested it locally?
• Have you run the linter (npm run lint) prior to submission? Enable the git hook on commit in your IDE to run it and format the code automatically.
• Have you run the tests locally and added/updated them if needed?
• Have you checked that app can be built (npm run build)?
• Have you made sure that all the necessary pipelines has been successfully completed?
• If the task requires translations to be updated, have you done this by running the manage:translations script?

Visuals

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 60.50%. Comparing base (e1cb3fb) to head (eb969e4).

Files	Patch %	Lines
app/src/common/constants/retentionPolicy.js	0.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3830      +/-   ##
===========================================
- Coverage    60.57%   60.50%   -0.07%     
===========================================
  Files           79       80       +1     
  Lines          865      866       +1     
  Branches       127      127              
===========================================
  Hits           524      524              
- Misses         314      315       +1     
  Partials        27       27              

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

[AmsterGet]

Let's follow the correct HTML structure and don't put block elements inside the inline elements.
I suppose the div here can be easily replaced by span.
W3C recommendation, community discussions