Remove project nodes from built-in list so they can be upgraded

[knolleary]

Part of #3816

Description

This removes project-nodes from our list of built-in modules. This list was used to filter what modules we'd present in the settings/palette view. However, by doing that, we made it hard for the user to update the nodes.

On reflection, there is nothing wrong with the user being able to see and edit the project nodes version. As a consequence of this change:

1. A user will be able to upgrade the project nodes in their instance (without needing a stack update)
2. If the user updates, the settings/palette view will list what they have installed.
3. If a user deletes project nodes from the settings/palette view and restarts, it will revert to the version of the nodes baked into the stack.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.10%. Comparing base (2173621) to head (f2c9529).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3834   +/-   ##
=======================================
  Coverage   79.10%   79.10%           
=======================================
  Files         279      279           
  Lines       12524    12524           
  Branches     2782     2782           
=======================================
  Hits         9907     9907           
  Misses       2617     2617           

Flag	Coverage Δ
backend	79.10% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.