- Create/update superuser
- Set wagtail site domains

```
❯ ./manage.py initialize
Provide the details below to initialize Hypha Site. Press enter to keep the default value.

Domain of public site  [hypha.test]:
Domain of apply site  [apply.hypha.test]:
Superadmin Email  [superadmin@hypha.test]:
Superadmin Password  [hypha123]:
Site port [8090]:
>>> Created superuser with email superadmin@hypha.test.
>>> Set public site to hypha.test:8090
>>> Set apply site to apply.hypha.test:8090
```

NOTE: The font files and `npm -> build:fonts` scripts are still kept as 
they are used by reportlab for rendering PDFs. 

The system font is not removed from the public site to keep up with the
OTF branding.

If not using custom fonts, the pdfs are rendered with
Helvetica. Let’s discuss whether we need to use custom fonts for the
PDFs.

Closes #3131

Partial fix of #3066
(https://github.com/HyphaApp/hypha/issues/3066#issuecomment-1337463266

)

- [x] We should rename "/apply/projects/4/simplified/" to something like
"/apply/projects/4/approval/". Also rename
"ProjectDetailSimplifiedView".
- [x] The link to the uploads contract in the "Contracts" box should
open in a new tab, "target _blank"
- [x] When an applicant uploads a signed contract an e-mail is sent to
the applicant but not to the "Compliance Email" address from project
settings. I do not think we need the mail to the applicant but need to
add one to compliance.
- [x] When a user has approved a PAF I think the PAF should be removed
from that users dashboard.(Multiple tabs to show already approved and
approval required).
- [x] E-mail should be sent out to 'contracting+approver' user's email
address when all "PAF Reviewers Roles" have approved a PAF. The project
should also show in a "Final approving requeried" table on the Dashboard
for Contracting+Approver users.
- [x] Fix misspelling of "venor", should be "vendor"
- [x] Fix Permissions for contracts(hide buttons).
- [x] Do we need to separate "Compliance Email" setting to one address
for finance users and one for contracting users? Or should we send
directly to address is user accounts that has the role in question? (We
decided email notifications could go to a 'group email' and default to
individual emails if group email is not provided)

---------

Co-authored-by: sandeep <sandeep@Sandeeps-MacBook-Air.local>
Co-authored-by: Saurabh Kumar <theskumar@users.noreply.github.com>
Co-authored-by: Fredrik Jonsson <frjo@xdeb.org>

Fixes #3139 

Remove 'filters-date' class for invoice filters on the overview page
because there is no date field in InvoiceListFilter.

…dev so files from dev packages are collected as well. Mainly
django-debug-toolbar.

Fixes #3143

https://www.djangoproject.com/weblog/2023/feb/01/security-releases/

Fixes #3105 

- This free up space at the top for batch actions.
- Also, add an indication of which per_page value is currently used.

Co-authored-by: sandeepsajan0 <sandeepsajan0@gmail.com>

Add personality and make things a bit clear. 

Fixed sentry issue
[3887915131](https://sentry.io/organizations/otf/issues/3887915131/?project=1268368)

#3123 has fixed it only for the users who can't see the archived feature
and that's why we found it working in our testing but for staff admin,
this issue is still there.

The main issue is we have checked for empty and None archived values but
with the search only it passes 'None' as the str type. I fix it by not
passing the archived param to the URL if the archived param's value is
None(not selected yet).

Initial Fix [hypha-issues#8
](https://github.com/HyphaApp/hypha-issues/issues/8

)

Co-authored-by: sks444 <krishnasingh.ss30@gmail.com>
Co-authored-by: Fredrik Jonsson <frjo@xdeb.org>

Fixes #3101

- Remove `make sort` and `make sort-fix` make targerts
- Use `make lint` and `make lint-fix` instead.
- Make use of GitHub Annotation to surface issues as annotations
directly in the files changed, similar to CodeQL.
- Move stuff from `setup.cfg` to `pyproject.toml`
- Fixed the potentially buggy code. Each of the fix types is in
individual commits.

Fixes #3070

Fixes #2506 

Fixes #2841 

Fixes #3047 

Co-authored-by: sandeep <sandeep@Sandeeps-MacBook-Air.local>

- Remove dependency on python-venv and python-pip
- update how to run test

Fixes #3021 

NEW_SUBMISSION is getting used to notify staff members on slack and also
to notify the applicant. But for draft submission, only the applicant
should get the notification, there shouldn't be any recorder activity or
slack notification.
So, added a separate event DRAFT_SUBMISSION that only sends the
notification/email to the applicant.

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

Fixes #2996 

- [x] Add archive function to batch action
- [x] Make submission tables archive aware, possibility to toggle
between all and active (unrachived)
- [x] Optional permission so only staff admins can see archived
submissions.

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

Fixes #3017

- [x] Add an "Digest recipient e-mails" field to each Fund and Lab.
Similar to the existing Slack channel field.
- [x] Create the same type of digest as the global one but filtered for
each Fund and Lab.
- [x]  Send out all digest with the same cron command.

---

![Screenshot 2022-11-03 at 08 38
25@2x](https://user-images.githubusercontent.com/236356/199677732-00ffbf24-4c58-410a-8f9c-1f03b82009c2.jpg

)

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

Bumps [json5](https://github.com/json5/json5) from 2.2.1 to 2.2.3.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/json5/json5/releases">json5's
releases</a>.</em></p>
<blockquote>
<h2>v2.2.3</h2>
<ul>
<li>Fix: json5@2.2.3 is now the 'latest' release according to npm
instead of v1.0.2. (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/299">#299</a>)</li>
</ul>
<h2>v2.2.2</h2>
<ul>
<li>Fix: Properties with the name <code>__proto__</code> are added to
objects and arrays.
(<a
href="https://github-redirect.dependabot.com/json5/json5/issues/199">#199</a>)
This also fixes a prototype pollution vulnerability reported by
Jonathan Gregson! (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/295">#295</a>).</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/json5/json5/blob/main/CHANGELOG.md">json5's
changelog</a>.</em></p>
<blockquote>
<h3>v2.2.3 [<a
href="https://github.com/json5/json5/tree/v2.2.3">code</a>, <a
href="https://github.com/json5/json5/compare/v2.2.2...v2.2.3">diff</a>]</h3>
<ul>
<li>Fix: json5@2.2.3 is now the 'latest' release according to npm
instead of
v1.0.2. (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/299">#299</a>)</li>
</ul>
<h3>v2.2.2 [<a
href="https://github.com/json5/json5/tree/v2.2.2">code</a>, <a
href="https://github.com/json5/json5/compare/v2.2.1...v2.2.2">diff</a>]</h3>
<ul>
<li>Fix: Properties with the name <code>__proto__</code> are added to
objects and arrays.
(<a
href="https://github-redirect.dependabot.com/json5/json5/issues/199">#199</a>)
This also fixes a prototype pollution vulnerability reported by
Jonathan Gregson! (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/295">#295</a>).</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/json5/json5/commit/c3a75242772a5026a49c4017a16d9b3543b62776"><code>c3a7524</code></a>
2.2.3</li>
<li><a
href="https://github.com/json5/json5/commit/94fd06d82eeed225fa172f6fb2ca27375cbd2e39"><code>94fd06d</code></a>
docs: update CHANGELOG for v2.2.3</li>
<li><a
href="https://github.com/json5/json5/commit/3b8cebf0c474a8b20c78bd75c89cca0c4dce84ce"><code>3b8cebf</code></a>
docs(security): use GitHub security advisories</li>
<li><a
href="https://github.com/json5/json5/commit/f0fd9e194dde282caff114a110f4fac635f3a62c"><code>f0fd9e1</code></a>
docs: publish a security policy</li>
<li><a
href="https://github.com/json5/json5/commit/6a91a05fffeda16ff6b3b5008b6b340d42d31ec0"><code>6a91a05</code></a>
docs(template): bug -&gt; bug report</li>
<li><a
href="https://github.com/json5/json5/commit/14f8cb186e8abdfaccf6527171da7b1224374650"><code>14f8cb1</code></a>
2.2.2</li>
<li><a
href="https://github.com/json5/json5/commit/10cc7ca9169b59c5e0f5afc03dbd870cd06bcc46"><code>10cc7ca</code></a>
docs: update CHANGELOG for v2.2.2</li>
<li><a
href="https://github.com/json5/json5/commit/7774c1097993bc3ce9f0ac4b722a32bf7d6871c8"><code>7774c10</code></a>
fix: add <strong>proto</strong> to objects and arrays</li>
<li><a
href="https://github.com/json5/json5/commit/edde30abd8b22facf2c06c72586b9f6edf12700d"><code>edde30a</code></a>
Readme: slight tweak to intro</li>
<li><a
href="https://github.com/json5/json5/commit/97286f8bd542c89dcee096bc05dd28ed2dfc1e16"><code>97286f8</code></a>
Improve example in readme</li>
<li>Additional commits viewable in <a
href="https://github.com/json5/json5/compare/v2.2.1...v2.2.3">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=json5&package-manager=npm_and_yarn&previous-version=2.2.1&new-version=2.2.3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the
default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as
the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as
the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the
default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/HyphaApp/hypha/network/alerts

).

</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Do not call `getattr` with a constant attribute value. It is not any
safer than normal property access.

The variables `reviewer` and `related` has the same as the iterable it
iterates on. This can lead to unexpected results.

It is generally not a good idea to perform function calls in argument
defaults in Python because the function will be called at the time the
default value is defined, not when the function is called. This means
that if the function has side effects, they will be executed every time
the default value is used, which can lead to unexpected behavior.

Replace their usages with the literal versions, [] for lists, {} for
dicts, etc. It's easier for others to read, looks nicer, and the
interpreter will convert it into bytecode that is executed faster
(special opcodes for the containers, instead of performing function
calls).

Within an except clause, raise exceptions with raise ... from err or
raise ... from None to distinguish them from errors in exception
handling

- Fix test for EmailMessage task
 - Add tablib dependency for Wagtail ExportAdmin
 - Fix DeprecationWarning for django_table2
 - Fix depreciationwarning for beautifulSoup
 - Fix RemovedInDjango41Warning for default_app_config
 - Fix DjangoRemovedIn4.0 warning Middleware always require a function
 - Upgrade boto3 and scout-apm
 - Update pytest-cov to 4.0.0 from 3.0.0
 - Upgrade djangorestframework-api-key to 1.2.0
 - Rename “app” to “apps”