checking 'well known' teams requires two queries at startup and in tests

This is because we:
 - load the team
 - do a membership check

If we did one query, always, we'd have less gradual memory bloat on the appservers, more test isolation. We could do this by querying for person, teamparticipation where person.name='teamname'. /If/ we need to cache this, we can cache it on the person by the name of the team : thats near enough to immutable to be quite reliable within a single request.

High because of the benefits to testing (query count tests) and appserver leanness.