remove any peerDependencies on packages other than hub-common

[tomwayson]

Fortunately it looks like it's just sites that has peerDependences on initiatives and teams.

That causes:

• us to have to keep those peerDependencies up to date manually at release time
• solution.js to depend on teams and initiatives even though it doesn't use them,
• solution.js maintainers to rely on often ignored console messages to know if they need to update teams or initiatives

Proposed solution:

• move getInitiativeTemplate(), addInitiative(), updateInitiativeSiteId() (and any fns they need) to common
• consolidate teams into common since it is relatively small and we'll want to do this for most if not all packages

[tomwayson]

NOTE: the above is true of teams in template-js too.

Furthermore, the processors package only depends on initiatives for getUniqueGroupName(), so maybe that can move to common too at this juncture and then template-js can drop the dependencies on both teams and initiatives.