… position on 16:9 mobile phone screen

…cent changes

chore: improve issue forms and use pre-commit hooks for validation

chore: always wait until all upgrades are available

By modifying `.gitattributes` to allow more tests to pass on Windows.

docs: update "Installing optional dependencies" section to reflect recent changes

**Description**

Currently, our Renovate configuration triggers a rebase for its open pull requests whenever they fall behind the `develop` branch. This is causing a significant number of unnecessary GitHub Actions workflow runs.

For example, we often have several Renovate PRs that cannot be merged immediately (e.g., #4547, #4429, #4066). Each time a new commit is pushed to `develop`, all of these PRs are rebased. Each rebase triggers its full suite of checks (around 20 workflow runs per PR). With just these three PRs, this results in approximately 60 workflow runs for a single commit to `develop`.

These CI runs are redundant because we are aware these PRs cannot be merged, and the constant rebasing provides no value.

**Proposed Solution**

I propose we modify our Renovate configuration to only rebase pull requests when they have a merge conflict with the base branch or when automerge is enabled.

This change is safe for our workflow. We have the GitHub Merge Queue enabled, which automatically runs checks on the latest version of the base branch before any PR is merged. This practice already protects the `develop` branch from failures that might otherwise be missed, making the pre-emptive rebases unnecessary.

**Expected Outcome**

*   A significant reduction in GitHub Actions minutes and associated costs.
*   Less CI noise and faster queue times for legitimate development workflows.
*   No degradation in the stability of our `develop` branch.

chore: configure Renovate to reduce unnecessary CI runs