Update Compose BOM to 2024.02.00. Fixes #1218

[dturner]

What have I done and why?

• Updated the Compose BOM from 2023.10.01 to 2024.02.00 (Compose 1.6.2)
• Updated deprecated/changed Material3 components in line with recommended guidance
• Fixed a couple of minor build warnings
• Replaced BoxWithConstraints with Box
• Changed font heights, alignment and spacing so that the current UI layouts stay the same. In Compose 1.6 (introduced by this BOM) includeFontPadding defaults to false. This causes some unwanted layout changes. To preserve the current UI I had to tweak the typography styles using LineHeightStyle and make some slight layout changes. The new layouts aren't a pixel perfect match (as can be seen in the screenshot diffs) but they are close enough so that no-one should notice.

Notes on screenshot diffing
Updating the layouts to match previous screenshots was a time consuming process. In case anyone else needs to do it, here's what I did:

• Clone the repo, checkout the commit/branch which contains the "old" screenshots i.e. the ones which are considered to be correct
• Record new screenshot tests./gradlew recordRoborazziDemoDebug --rerun-tests. Note the --rerun-tests ensures that new screenshots are actually recorded, without it I would sometimes find that they weren't updated despite code changes
• Copy the screenshot(s) folders to "screenshots-old" in the same parent folder - this is to move them out of source control
• Checkout your current branch (the one which will contain the new screenshots), make UI changes and record new screenshots
• Use Beyond Compare 4 to do a folder comparison between the old and new screenshots folders. It has some extremely useful features like being able to offset one image on the other and do a pixel by pixel comparison with surrounding pixels:

[JoseAlcerreca]

Looks like if you re-run a job after the screenshots were generated, it fails when trying to commit the new ones. Can you add another commit or force-push without the 9e64 commit?

[LinX64]

Looks like if you re-run a job after the screenshots were generated, it fails when trying to commit the new ones. Can you add another commit or force-push without the 9e64 commit?

As a note, a rebase is required to apply the changes from your previous merged PR about CI to solve the emulator issue, please see here.

[alexvanyo]

Thank you for the detailed description for the text style changes! Resulting screenshot changes look good, either barely noticable or strictly an improvement (like the navigation bar one at large font scales)