Feature/carousel runtime calculation

[GodKratos]

📝 Description

The recently requested carousel uses hard coded display settings to adjust how item cards are displayed. These settings do not produce a good display and the width override of the other carousel views causes the scrolling of the items to either cut off early or too late depending on the width of the screen.

This PR adjusts the way the recently requested carousel is displayed by doing the following:

• dynamically sets the numVisible and numScroll parameters of the Recently Requested carousel based on the window size and the item card size (when adjusted for mobile view)
• removes the width override of the carousel items so that the scrolling size of items matches the item size (this fixes the issue of scrolling not matching the contents)
• centres the contents of the carousel items to look better

📸 Screenshots (if applicable)

Before the Change:

Carousel scrolling would stop early cutting off the last item:

After the Change:

Carousel items scroll evenly no matter the window size:

[tidusjar]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sonarqubecloud]

Quality Gate passed

Issues
0 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 SonarQube Cloud

[tidusjar]

Thanks for this, please ignore the failing status checks, everything is passing but it doesn't have permissions to update the PR (i'll sort that).

I'll review soon