Plan how to add testing sessions functionality to existing code

[MikhailDeriabin]

There should be created a plan how to integrate the requirements of the testing session to the existing API.

All the functionality of the group admin can be found here:

On stage 2

On stage 3

The main problem here is, that the box should limit access to its resources from outsiders. For example:

/clan GET is returning all clans existing => the boxes are not isolated from each other, since this query should only return 2 clans created for the current box.

The same problem is with /player, profile, stock etc., almost with everything.

Obvious solution could be to add some if-else statements:

if( environment === 'TESTING_SESSION' ){
  // return clans only for this session
} else {
  // work as usual 
}

This solution is straight forward, but this means that almost every controller method should be changed to same manner, and it is not the most optimal one, especially if there will be a need to remove all of them from code after couple of months or so.

It is possible that the if-else is the only one.

Solution, if any, can be placed to docs folder (diagrams or .md files)

[MikhailDeriabin]

Change Services that are injected to controllers, so based on the .env