Use audit events to improve management of node module list

[knolleary]

Fixes #2005

Description

The existing code to keep the platform's record of modules installed in an instance relied on the event triggered when Node-RED saves its node list.

That event isn't triggered when a module is upgraded - meaning the platform's record gets out of date.

The fix is to use the nodes.install audit event which does get triggered for the upgrade path.

I've also added support for the nodes.remove audit event to trigger removing modules from the list.

Whilst there, I've modified the test suite to only run setup once, rather than before each test. This only required updating the names of the projects the individual tests were creating to ensure uniqueness.

When running the tests locally, this reduced the runtime for the _spec file from 7s to 2s - a good step in the right direction for #2004

Related Issue(s)

Acceptance Criteria

On staging:

• Update an out-of-date module on Node-RED Palette manager
• Check that the list of installed modules on the instance settings in FF has updated.

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on flowforge/helm to update ConfigMap Template
  • Issue/PR raised on flowforge/CloudProject to update values for Staging/Production

Labels

• Backport needed? -> add the backport label
• Includes a DB migration? -> add the area:migration label

[Steve-Mcl]

Looks sane.
Will check/update acceptance criteria to ensure specific manual operations are performed to test this on staging.