Bulk-edit(Users) move tests run to test tenant

Purpose/Overview:
Currently, tests are run against the diku tenant by the broken behavior of data-export-spring/worker in multi-tenant environment.

1) In the scope of this story, it is required to enable test tenant creation and setup/run tests against this test tenant as other API tests do it.
2) The user "active" field behaves weirdly in snapshot env. After the update job that changes the field from false to true, the value of the field is set from true to false back by the system automatically, and after several seconds the value turns back to be true. It breaks the consistency within tests.
In the karate tests environment this issue is absent but the field was omitted from expected JSON matching in order to have the possibility to verify tests manually using snapshot env or automatically with the karate tests pipeline.
The expected value should be moved back for verification with JSON comparison, therefore both files with expected users expected-users-preview-after-identifiers-job.json and expected-users-preview-after-update-job.json should have this field presented within users JSON bodies.

Approach:

There are TODO comments in the code, follow the instructions described in them.

Acceptance criteria:

• Bulk-edit API tests run against test tenant