Mypy type errors fix

[Domejko]

Description

Fixed all type errors in settings/ folder reducing there number from 384 to 369 errors.

Edit:
Part of files in backend/ also have been fixed and errors count is reduced to 354.

Edit:
Mypy error count reduced from 354 to 313.

Created utils/ folder, refactored utils.py to different files and updated imports accordingly.
Added new subclass of HttpRequest reduce type errors as suggested in django-stubs documentation.

Edit:

• Resolved merge conflict due to feature: invoice reminders #339 update
• Moved event_bridge_scheduler inside the function to call when needed due to

ValueError: If using schedules, the variables MUST be set.

• as in bug: Failed to launch app #321

Checklist

• Ran the Black Formatter and
  djLint-er on any new code
  (checks
  will
  fail without)
• Made any changes or additions to the documentation where required
• Changes generate no new warnings/errors
• New and existing unit tests pass locally with my
  changes

What type of PR is this?

• 🐛 Bug Fix
• ♻️ Code Refactor

Added/updated tests?

• 🙅 no, because they aren't needed

Related PRs, Issues etc

• Related Issue MyPy Error Fix | Open to all #319

[TreyWW]

There's a few minor issues I found with this PR but overall well done! Thanks for the contribution, would appreciate some changes made though :)

[Domejko]

New commit with requested changes have been pushed.

[Domejko]

If you approve recent changes I think we should merge those changes since this issue is open to all to participate so we need to avoid cases when someone else will try to handle errors that have been already resolved in this PR.

[Domejko]

So I think I'm going to hold off on correcting errors until #339 will be implemented.

[TreyWW]

Thank you

[TreyWW]

Thanks for the wait. PR #339 has been merged

[Domejko]

Ok, tomorrow I'll resolve conflicts and as soon as this PR will be merged I will proceed with work on the rest of errors.

[TreyWW]

Amazing, sounds good

[Domejko]

Regarding changes. If there will come features in the future that will be using @login_required decorator then instead of regular HttpRequest should be used AuthenticatedHttpRequest from backend/utils/http_utils.py. This will prevent mypy from throwing error about AnonymousUser type.

Also what do you think about moving HtmxHttpRequest subclass from backend/types/htmx.py to backend/utils/http_utils.py. Or maybe other way around, moving AuthenticatedHttpRequest to backend/types/ as authenticated_http.py.

[TreyWW]

All views are login required, we just use middleware instead of @login_required

[TreyWW]

As for the second part of the comment, I'm not too sure. I feel like the utils file should be for logic, rather than type definitions. Wherever the HTMX request is we could add a user object to that? And then add a second one if we use htmx without login required? We could talk more on discord if you'd like, may be easier

[Domejko]

Yes sure, my username is domejko_

[TreyWW]

Amazing PR, thank you!