IdeaFlow engine - Refactor TeamBoxConfigurations into ProjectBoxConfigurations

[accolasia]

Now that organization members can be on multiple teams, Idea Flow individual feeds can't be team specific, so need to refactor this logic so that the box configurations (component mappings for files) applied for a tile comes from the project, not the team.

Since the Idea Flow aggregation is still done per team, and the members can be on multiple teams, whenever the member tile is generated, all the teams that the user is on will need to receive an aggregation event. Then we will need a way for the team to specify what projects they're interested in, even if team members are working on other projects for other teams...

So maybe a team projects list? Something like that. Applied at the team level as a filter on top of the individual feeds.

[accolasia]

Box configurations now directly associated with projects, and will use the project context of the active intention to lookup the box mapping for the file. Since the projectId is part of the box search key for the feature, this should work fine as a global scope key.

The aggregation for teams will end up being across all projects. If these need to be filtered later, we can do that, but should be fine for a first cut implementation.