Update to Django 3.2.13.

Update required fields error message

Hide the status section on public project pages.

Merge pull request #2797 from HyphaApp/enhancement/remove_status_obsolete_info_from_application_project_detail_page

Remove obsolete information from the application project detail page.

Populate "E-mail" and "Full name" on submissions and disable input for the logged in users

Make duration field optional and set required None for existing data

Update error messages z-index(css)

Fix change email error

Bump minimist from 1.2.5 to 1.2.6

Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6.
- [Release notes](https://github.com/substack/minimist/releases)
- [Commits](https://github.com/substack/minimist/compare/1.2.5...1.2.6

)

---
updated-dependencies:
- dependency-name: minimist
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Bump node-forge from 1.2.1 to 1.3.0

Bumps [node-forge](https://github.com/digitalbazaar/forge) from 1.2.1 to 1.3.0.
- [Release notes](https://github.com/digitalbazaar/forge/releases)
- [Changelog](https://github.com/digitalbazaar/forge/blob/main/CHANGELOG.md)
- [Commits](https://github.com/digitalbazaar/forge/compare/v1.2.1...v1.3.0

)

---
updated-dependencies:
- dependency-name: node-forge
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Users without a `slack` field could not change their email address due
to the fact that doing so would attempt to set the slack column to null
(and nulls are not allowed).

This updates the save of the change email field to only modify the slack
value if it exists.

Issue #2784 Changing email on non-staff accounts creates non-null
            constraint violation

USe both requirements-dev and requirements for cache key.

Update circle ci cache number and update to node 16.x.

Add help text about information being fetched from account. Add css for disabled input fields, was in apply but not in public.