Fixes #3887 

Fixes #3939

Some left/right/top/bottom had slipped past.

Fixes #3895. Quick one I noticed while working on the partner comment
stuff. Comments will now display with the user email where no full name
is set.

- [x] Add approved by staff to the approved invoice pdfs
- [x] Add inovice approver and date

Closes: https://github.com/HyphaApp/hypha/issues/3539

Fixes #3923 

Fixes #3927 

Fixes #3839 

##  Assumptions

An organization only chooses one option either go with PAFReviewerRoles
or without that. Changing in between might cause the issue with
`Internal Approval` status projects. We will fix this in another issue
if needed.

- Rename "Apply Admin" to "Admin" 
- Adds "Admin" icon to the user's profile page along with the
"Dashboard" link, makes it easier to goto admin without going to
dashboard everytime first.
- Update icons for "dashboard" and "Admin" to use heroicons.
- Update activity feed related link icon + it's visuals
- Remove `arrow-head-pixels--solid` icon from the sprite as it's no
longer in use anywhere.


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

Fixes #3840 

Fixes #3889

- do not register project urls
- do not register project menu in wagtail
- do not enable contracting/finance dashboard

Fixes #3606

Project settings and vendor settings will still be present, I could not
find a way to hide/disable them conditionally.

Fixes #3897

"Remember me" is only available when logging in with password. I see
this as an "advanced" feature. The passwordless login flow is easy so
not a big hassle to do it once a day.

Organisation that wants to can set `SESSION_COOKIE_AGE` to a custom
value, e.g. set it to two weeks to reagin the old behaviour.

To disable "Remember me" set `SESSION_COOKIE_AGE` to the same value as
`SESSION_COOKIE_AGE_LONG`

This PR also:

* removes unused code is_public_site
* removes unused code register_extra_text
* removes all use of link-button* classes. Buttons are now only handled
by the button class.
* add a tiny border radius to all buttons (this is something we
implement on all elements in Hypha)

Fixes #3892. This solution was a bit unruly (especially ugly after
linting) but it seemed like the logical approach without refactoring the
whole `visibility_for` to be a normal method rather than a class method.
This fix evaluates if the partner/reviewer is the author of the source
submission first before evaluating the their role. The reviewer role was
also lumped in here because even though I know we advise against a
reviewer also being an applicant, it still could happen without
oversight.

I tried to keep the code as clean as I could and reuse QuerySets, but
let me know if y'all see any way I can optimize!

Fixes #3849 

Fixes #3886

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

Also, refractor and allow for importing permission functions from
anywhere and not just limit to be imported from the
`hypha.users.decorators` module

This PR also doesn't display project info on the dashboard if the
projects is not enabled

For the stats block at the top of the dashboard, if the projects is not
abled displays the count of flagged submissions and the count of
previously reviewed submissions

Simplify the nav generator logic. 

With `PROJECTS_ENABLED = True`, Project Report Forms may now be
created in Wagtail Admin and associated with a Fund.

Project reports use the form configured in Wagtail admin. To add or
edit a report form, use `Projects -> Report Forms`. To bind a report
form to a given Fund, use `Apply -> Funds`, set `Project Report Form`.

When projects are enabled, a project shows the Reports in various
project interfaces. A new project report will use the current fields
from the Project Report Form associated with the Fund from which the
Submission/Application was granted. An existing report, when edited,
will use the original fields at the time that report was first filed.
This behavior appears consistent with at least one other similar form.

Thanks to Frank Duncan for the "View" functionality in
hypha/apply/projects/templates/application_projects/report_detail.html
and NonFileFormFieldsBlockFactory for tests that don't need files
as well as re-adding the url for project file lookup by id.

Co-authored-by: Frank Duncan <frankduncan@opentechstrategies.com>

---------

Co-authored-by: Jesse Bickel <bickelj@gmail.com>
Co-authored-by: Frank Duncan <frankduncan@opentechstrategies.com>

Due to djhtml the emails templates where formatted with indendation.
That lead to alignment also being present in the plain-text emails.

This was an unintentional behaviour that this PR fixes by adding {#
fmt:off #} markers in the email templates so djhtml won't format them

- [x] Convert toggle-related.js to vanillajs.
- [x] On submission detail convert toggle-actions-panel.js to alpinejs.
- [x] Convert submission-text-cleanup.js to vanillajs.
- [x] Replace dropdown.js with alpinejs.
- [x] Convert all-submissions-table.js to vanillajs.
- [x] Convert application-form-links-new-window.js to vanillajs.
- [x] Made PAF and SOW views and download buttons to look the same.

- ~Change the background of the page to light grey~
- Add border to each of the tasks

Fixes #3828 

Fixes #3875. 

Switches order to date submitted in `Related Submission`'s
`Past Submissions`

The messages display below the opinion buttons looks like part of the
rest of the form display

This PR add styling so the info displayed is little different

Fixes #2685

Fixes #3782.

Rather than having `is_staff` set to true when a user's
email is the org's domain, this sets it true when a user is Staff Admin
or a Superuser. Also includes a migration to handle existing cases where
Staff Admins are not `is_staff`.

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

Inline error messages

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

Fixes #3861 

Fixes #3788 and a few other issues. The main problems being seen around
the preview were when it came to the edit view. This was because the use
of the `Draft` status was being relied on for the saving of content
before previews, when realistically a new application revision had the
same effect.

Previously, Admins/Staff could submit new applications, but could not
submit existing applications. This is why when an Admin had attempted to
submit a preview or submit an edited application, they could not do so.
This functionality has been moved from `ApplicantSubmissionEditView` to
`BaseSubmissionEditView` as it made sense to me that Admins would be
able to access the same edit workflow & transitions as Applicants. I
believe most OTF staff avoid editing incoming applications though.

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

Adds a max-height and overscoll to the dropdown items 

Fixes #3857. Swaps the `Open` & `Closed` tabs in the beta round filter.
This also ensures that the closed tab will be selected if there are no
open rounds.

Fixes
https://otf.sentry.io/issues/5013342091/events/e636f260d01640e897414eec5ac884eb/

Looks like we have deleted something from the test site and that
shouldn't be the case in prod but still no harm to have better error
handling.

Fixes #3863

Fixes these issues:

* The flagg views are not updated with the new adminbar component.
* Staff flagged view are not included in the main menu.
* Unflagging submissions did not work in the user and staff flagged
views, only on dashboard.
* Staff flagged filter was missing from new all-beta view.

Fixes part of #3537

- Update requirements
- Replace classnames with classname
- update wagtail admin page of `settings -> users`

closes #3674