fix(app/frontend): server card text overflow, jump-in card cutoff, close button hover

[Ceebug]

Fixes for app/frontend:

Fix text overflow of cards in the 'Jump In' page that happens when the text in the player count area gets too long.
Fix server and world cards in the 'Jump In' page being cut off when the window is small enough.
Fix close button not changing its background to red on hover (#7627)

[github-actions]

Pull request changelog

App

Added

Changed

Deprecated

Removed

Fixed

• Fixed close button not having a red background on hover.
• Fixed "Jump in" cards overflowing when the window is small.

Security

Website

Added

Changed

Deprecated

Removed

Fixed

Security

Hosting

Added

Changed

Deprecated

Removed

Fixed

Security

[Prospector]

@Mergifyio queue

[mergify]

Merge Queue Status

• 🟠 Waiting for queue conditions
• ⏳ Enter queue
• ⏳ Run checks
• ⏳ Merge

Waiting for any of

• check-neutral = Lint and Test
• check-skipped = Lint and Test
• check-success = Lint and Test

All conditions

• any of [🔀 queue conditions]:
  • all of [📌 queue conditions of queue rule default]:
    • any of [🛡 GitHub branch protection]:
      • check-neutral = Lint and Test
      • check-skipped = Lint and Test
      • check-success = Lint and Test
    • github-review-approved [🛡 GitHub branch protection]
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of [📌 queue -> configuration change requirements]:
  • -mergify-configuration-changed
  • check-success = @mergify/Configuration changed
  • check-success = @mergify/Configuration has been deleted
• any of [📌 queue requirement]:
  • check-neutral = @mergify/Mergify Merge Protections
  • check-skipped = @mergify/Mergify Merge Protections
  • check-success = @mergify/Mergify Merge Protections

[Prospector]

@Mergifyio rebase

[mergify]

rebase

❌ This pull request comes from a fork and cannot be rebased

Details

GitHub refuses an OAuth token on its rebase API for a fork, so rebasing one means impersonating a GitHub user to force-push the contributor's branch. Mergify does not do that.

Use the update action or the @mergifyio update command instead: it brings the pull request up to date by merging the base branch into it, and needs no impersonation. It only has something to do when the pull request is behind its base branch, so if what the branch needs is a linear history, its author has to rebase it themselves.