Ensure that users cannot be added to "New" / "Inactive" / "Archived" projects

[matthew-li]

Check whether users can be added to a Project with the "New", "Inactive", or "Archived" statuses (i.e., answer the following two questions):

1. "Can a user request to join such a project from the UI?"
2. "Can a PI/manager of such a project add users to such a project?"

If so, prevent it.

• Update the UI (e.g., disabling buttons) and prevent join/add actions from within the back end views.
• Consider either adding explanatory text to the page, or a tooltip when a button is hovered over.
  • Note, however, that "Archived" projects should not even appear in the UI.

In either case, document in this issue (or a PR) the exact behavior (both in the UI and on the back end) preventing these actions.

[haudquaquam]

1. "Can a user request to join such a project from the UI?"
   • A user cannot access a Project that is "New," "Inactive," or "Archived" from the "Join a Project" page. Only "Active" Projects are listed.
   • Users also cannot access "New," "Inactive," or "Archived" Projects by going to /project/##, where ## represents the project ID of a Project.
2. "Can a PI/manager of such a project add users to such a project?"
   • For a "New" Project, no. The PI of a "New" Project can access the "Add a User" button and go through the flow of adding a user, however upon submission, the following error message shows: Project does not have a LBL Project ID for billing. You cannot add users until one is set.
   • For an "Inactive" Project, yes. The PI can access the "Add a User" button and successfully add a user. This probably should not be allowed.
   • For an "Archived" Project, no. The PI cannot make any changes to an "Archived" Project.