Enforce limits on number of teams that can be created

[knolleary]

Closes #778 #955

This limits how many teams can be created on the platform.

The limit is applied in the beforeCreate hook of the Team model.

There are three ways a team can be created:

1. A user creates a team - this is policed via the beforeCreate hook and an error returned to the ui
2. An admin creates a user and ticks 'create personal team' - by the time it comes to create the team, the user has already been created - so too late to reject the request. So this does its own check of the limit before attempting to create the user.
3. A user registers on the platform and the 'auto-create team' option is enabled - same as above (does explicit limit check)

Aside: for 2 & 3, I identified a bug (#955) that was stopping them from working. This PR addresses that bug by ensuring the TeamType is set on the projects they create. In fact, I have added a beforeCreate check to ensure TeamTypeId is always provided when creating a team. This required a couple tests to be updated as they weren't doing so.

[Steve-Mcl]

all good

[Steve-Mcl]

@knolleary code looks fine but there is an error in Project Lifecycle test...

Project Lifecycle
       "before all" hook for "login user":
     Error: Cannot create team without TeamTypeId
      at Function.beforeCreate (forge/db/models/Team.js:21:27)
      at Function.runHooks (node_modules/sequelize/lib/hooks.js:94:18)
      at model.save (node_modules/sequelize/lib/model.js:2378:30)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async Function.create (node_modules/sequelize/lib/model.js:1344:12)
      at async Context.<anonymous> (test/system/100-project-lifecycle_spec.js:51:29)

Can I ask if this ran ok under SQLITE locally?

[knolleary]

@Steve-Mcl fix pushed. I verified the unit tests but overlooked the system test folder when looking for calls to Team.create that needed updating.