Added to tests for the revoke access to a view API call
(DELETE /banks/BANK_ID/accounts/ACCOUNT_ID/users/USER_ID/views/VIEW_ID)

The scenarios were:
- revoke access to a random user
- revoke access to a view that does not exist
- revoke access to a user but without enough rights
Fixed problem with default user (tesobe@tsobe.com)
1) implemented the following API calls with their corresponding tests:
  - GET /banks/BANK_ID/accounts/ACCOUNT_ID/VIEW_ID/other_accounts
  - GET /banks/BANK_ID/accounts/ACCOUNT_ID/VIEW_ID/other_accounts/OTHER_ACCOUNT_ID
  - GET /banks/BANK_ID/accounts/ACCOUNT_ID/VIEW_ID/other_accounts/OTHER_ACCOUNT_ID/metadata
  - GET /banks/BANK_ID/accounts/ACCOUNT_ID/VIEW_ID/other_accounts/OTHER_ACCOUNT_ID/public_alias
  - POST /banks/BANK_ID/accounts/ACCOUNT_ID/VIEW_ID/other_accounts/OTHER_ACCOUNT_ID/public_alias
  - GET /banks/BANK_ID/accounts/ACCOUNT_ID/VIEW_ID/other_accounts/OTHER_ACCOUNT_ID/private_alias
  - POST /banks/BANK_ID/accounts/ACCOUNT_ID/VIEW_ID/other_accounts/OTHER_ACCOUNT_ID/private_alias

2) added the access test of the management view if the permittedViews method
1) Added for the private and public alias the two API calls providing
PUT and DELETE
2) refactored the tests to make them more modular
Merge branch 'api1.2' into develop