Implement proper rule processor version control

[Sandy-at-Tazama]

Automation:

During the release of a new version of Tazama (dev to main):

1. When the rule processor is merged to main, automatically publish a new npm package for the rule processor in the GitHub package registry. The version of the rule processor package can be a "natural" version increment and does not have to be forced to match the release version.
2. When the code for the rule executer is merged to main, automatically publish a build image of the rule-executer for each rule processor in Tazama to DockerHub. The version of the rule executer in the package.json must also be the release version. The default rule processor in the main branch version of the rule-executer must be rule-901. The version of the rule processor image must be the release version (upcoming 2.1.0). Side-note for future reference: if any between-release patches are made to a rule processor (or the rule-executer), the patch number of the version will be incremented (i.e. v2.1.0 to v2.1.1) on the assumption that a new release version of Tazama will never be a patch and will always be at least a feature release version (i.e. v2.1.0 to v2.2.0)
3. Update the configuration files to reference the correct release versions of the processors in the network map and rule configurations. (Product team action - manual, not automated)
4. Update the Full-Stack-Docker-Tazama docker-compose files to reference the current main branch version of the DockerHub images (i.e. the release version).