Allow for better type hints when working with editors that support it.
I'm using Zed with pywright linter. Recently, some type hints were added
to the project. This help catch issues against the django default types
and any custom types that are added to this codebase.

This doesn't add any runtime overhead.

This PR also these patch versions of these dependencies

- Updated anyio v4.6.2.post1 -> v4.7.0
- Updated boto3 v1.35.76 -> v1.35.79
- Updated botocore v1.35.76 -> v1.35.79
- Updated coverage v7.6.8 -> v7.6.9
- Updated django-select2 v8.2.1 -> v8.2.3
- Updated httpx v0.28.0 -> v0.28.1
- Updated mkdocs-material v9.5.47 -> v9.5.48
- Updated numpy v2.1.3 -> v2.2.0
- Updated sentry-sdk v2.19.0 -> v2.19.2
- Updated sqlparse v0.5.2 -> v0.5.3


https://github.com/typeddjango/django-stubs

Fixes #4265

Fixes #4274

Fixes #4270

---------

Co-authored-by: Saurabh Kumar <theskumar@users.noreply.github.com>

Also clean out unused styling items.

With new dart sass and `@use` instead of `@import` it is not possible to
override sass variables in a separate file. Using css variabels make it
possible again, even easy.

…that now defaults to A4. Improv styling, docx export do not support
rowspan.

Fixes #4259

Translations update from [Hosted Weblate](https://hosted.weblate.org)
for [Hypha/Hypha
core](https://hosted.weblate.org/projects/hypha/hypha-core/).



Current translation status:

![Weblate translation
status](https://hosted.weblate.org/widget/hypha/hypha-core/horizontal-auto.svg

)

Co-authored-by: Jiří Podhorecký <j.podhorecky@volny.cz>

Fixes https://github.com/HyphaApp/hypha/issues/4260

This makes sass sourcemaps work in development.

The flow to update are as follow:

1. Run `uv tree -d 1 --outdated` to get  list of packages with updates.
2. Update the package version in `pyproject.toml`
3. Run `uv sync`, this will install all the new packages and sync the
`uv.lock` file.
* The command will alert of any dependency conflicts, you need to
resolve these.
4. Run `pre-commit run --all-files`, this will run the `uv` commands
needed to update all the requirements* files. (Info is taken from the
`uv.lock` file so it must be updated before this step.)

Fixes #4256

Fixes #4252

Hopefully this is the last of it.

- Refractor to use base-pdf.html
-  Fix html tags rendering in pdf
- Refractor pdf rendering logic of PAF
- Convert PDFSetting to be a generic setting
- Upgrade xhtmltopdf to latest

Building off of the conversation had in #4051, this adds the navigation
to the reporting table to be under the submitted reports view rather
than being in the main nav bar

This makes things a little simpler and explicit for the user but I think
this is a temp fix, with #4239 being a permanent solution

Fixes #4117 

- [ ] Use htmx/alpine for Invoice status update modal
- [ ] Use htmx/alpine for report frequency update modal
- [ ] Use htmx/alpine for Update project status modal( Closing and
Complete)
- [ ] Use htmx/alpine for lead update modal
- [ ] Use htmx/alpine for project title modal
- [ ] Remove fancybox for report save, sabmit and skip confirmation.
- [ ] Remove fancybox imports from project code

Fixes #4246

- Use frozen dependencies with hashes to ensure reproducible dependency
installation in a secure way.
- Uses `uv` and pre-commit to automatically generate the locked
requirements files from pyproject.toml.
- While the translation dependencies can be installed directly with
`uv`, uv doesn’t seem to be able to add `--find-link=…` to the exported
`requirements/translate.txt`, for that reason the translation
dependencies are left as they are and won’t be automatically exported
via pre-commit.
- So whenever `uv lock —upgrade` is run, it will freeze the latest patch
versions.
- The production dependencies are specified with a `~` which means `>=`
at the last digit of requirements.
- The dev dependencies have `>=` to make them easy to update, if
something breaks in dev either fix it or go back to the old frozen
dependencies.
- Moved generated dependencies in requirements/ folder.
- Use `--no-deps` where applicable while installing these generated
requirements as the sub-dependencies are already resolved.

The js files are not update in the repo after node packages update

Translations update from [Hosted Weblate](https://hosted.weblate.org)
for [Hypha/Hypha
core](https://hosted.weblate.org/projects/hypha/hypha-core/).



Current translation status:

![Weblate translation
status](https://hosted.weblate.org/widget/hypha/hypha-core/horizontal-auto.svg

)

Co-authored-by: Jiří Podhorecký <j.podhorecky@volny.cz>

Translations update from [Hosted Weblate](https://hosted.weblate.org)
for [Hypha/Hypha
core](https://hosted.weblate.org/projects/hypha/hypha-core/).



Current translation status:

![Weblate translation
status](https://hosted.weblate.org/widget/hypha/hypha-core/horizontal-auto.svg

)

---------

Co-authored-by: Jiří Podhorecký <j.podhorecky@volny.cz>

Translations update from [Hosted Weblate](https://hosted.weblate.org)
for [Hypha/Hypha
core](https://hosted.weblate.org/projects/hypha/hypha-core/).



Current translation status:

![Weblate translation
status](https://hosted.weblate.org/widget/hypha/hypha-core/horizontal-auto.svg

)

Co-authored-by: Fredrik Jonsson <fredrik@combonet.se>

Fixes #4217

It is more of a development related change. Now it stores the
form_fields in Report table instead of ReportVersion so it will avoid
duplicity, nothing should change in UI.
You may still check that submitted report fields and data should remain
unaffected on changing the report stream fields form.

This workflow is like Request with External Review, in that both
internal and external reviewers can review submissions. However, it has
a workflow more like Request in that there is only one Review step.

Co-authored-by: Fredrik Jonsson <frjo@xdeb.org>

Fixes #4228. Makes hypha more printer friendly by not printing user
menus, the cookie consent prompt, or the hijack prompt.

Read up on DJP at https://djp.readthedocs.io/

The current implementation tries to find the transition based on the
`name` property of the transitions available. The name of the transition
is a translated string so while submitting a proposal the key "submit"
from the `request.POST` could not be found in the available transition.

This PR updates the logic to fetch the transition target, by searching
through the newly added marker on when to auto transition if the
application is submitted.

Fixes #4211 

See
https://github.com/HyphaApp/hypha/pull/4220/commits/e6656d62f6db57426bb15f298127c106ea4f6397
for patch.

This should resolve weblate's merge conflict issue along with adding
some of the latest translations into hypha's locales folder

Fixes #3891

Somehow this got reintroduced in my translate feature rebasing

This builds on the #4134 PR that initially introduced machine
translations into Hypha. This isolates the translation behavior; putting
pip dependencies in a separate `requirements-translate.txt` and will not
attempt any translate imports unless the setting for it is true.

Other small changes are also a full docs page explaining how to install
language packages & changing the setting once again from
`SUBMISSION_TRANSLATIONS_ENABLED` to `APPLICATION_TRANSLATIONS_ENABLED`
to reflect the system wide shift away from submission terminology.