scenario card arrows added

[Pawandeep-Kaur-Betz]

issue #147

There are problems of showing the arrows with the Recovered compartment.

[github-actions]

Unit Test Results

  1 files  ±0  12 suites  ±0   31s ⏱️ +4s
30 tests ±0  30 ✔️ ±0  0 💤 ±0  0 ❌ ±0 
31 runs  ±0  31 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 791e32c. ± Comparison against base commit d45a012.

♻️ This comment has been updated with latest results.

[coveralls]

Pull Request Test Coverage Report for Build 3205575528

• 0 of 3 (0.0%) changed or added relevant lines in 1 file are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.5%) to 20.145%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
frontend/src/components/ScenarioCard.tsx	0	3	0.0%

Files with Coverage Reduction	New Missed Lines	%
frontend/src/components/Sidebar/DistrictMap.tsx	2	0%

Totals
Change from base Build 3204973303:	0.5%
Covered Lines:	231
Relevant Lines:	905

---

💛 - Coveralls

[NXXR]

There are a few things that need to be addressed before merging:

• run formatting (npm run format) to make sure the code is properly formatted and passes the DevOps pipeline
• fix the lince height of the compartments (the changes result in scenario card compartment entries with more space between rows which lead to a mismatch between the header rows and the compartment rows:
  
• address the changes suggested/mentioned by Martin in the last Sprint meeting (changing the "positive" direction/color of the arrows & adding a neutral option, changeing how incremental values are handled)

[Pawandeep-Kaur-Betz]

As discussed, to change condition of grey arrow. It should show when the change is not significant or less than 1%

[Pawandeep-Kaur-Betz]

• Stagnation rule applied, grey arrow will show up if the change is more than 3%.
• Arrows also showing up on the basis of compartment value for those cases where RKI values are 0.