Page Comparison

Remove call to "/groups" api (i suppose it's even not used now)

Note: actually this is not a part of this spike, just wonder whether this api call is dummy. If so - it should be removed, but spike can be completed without this.

Rework "GET /kb-credentials/{kb-credentials-id}/users" api:

• get assigned users from db (only user ids by kb_credentials_id)
• query users info from `mod-users` for assigned users using "/users" api and cql (Check the max possible amount of users we can query this way and implement batches so if for example we have 200 assigned users in db and the limit is 50 then we should execute 4 queries with 50 users each and compose results then)
• query groups info using "/groups" api of  `mod-users`
• aggregate received info and pass as response

Update "POST /eholdings/kb-credentials/{kb-credentials-id}/users":

• remove "firstName", "lastName", "patronGroup", "userName" from api
• update repository interaction (save only kb_id to user_id relation)

Update call to "POST /eholdings/kb-credentials/{kb-credentials-id}/users":

• remove "firstName", "lastName", "patronGroup", "userName" from request body
• also do not depend on this fields in response

Schema updates:

• remove `kb_users` table from db
• remove `assigned_users_view`
• update `assigned_users` constraint(user id is a foreign key now, but users table will be removed)
• update `access_types` (remove view, constraints)

Code updates:

• remove unused repository
• update repository for new schema
• remove other unused code related to user data
• rework 'access-types' api to query user-related data from '/users' api of mod-users instead of database