SONARCLOUD-213 rename classes related to auth by credentials
- rename "Authenticator" to "Authentication"
- add a bit of javadoc
- highlight the relations
BasicAuthentication
|- UserTokenAuthentication
|- CredentialsAuthentication
|- CredentialsExternalAuthentication
|- CredentialsLocalAuthentication
SONAR-10597 Update MANUAL_MEASURES#USER_LOGIN to USER_UUID
* SONAR-10597 Update MANUAL_MEASURES#USER_LOGIN to USER_UUD in DB
* SONAR-10597 Update api/custom_measures/create to use user uuid
* SONAR-10597 Update api/custom_measures/update to use user uuid
* SONAR-10597 Remove CustomMeasureDao#selectOrFail
* SONAR-10597 Update api/custom_measures/search to use user uuid
* SONAR-10597 Clean up no more needed code
* SONAR-10597 Add ITs to check manual measure after login update
SONAR-10598 Display warning page when detecting login update during authentication
* SONAR-10598 Refactor UserIdentityAuthenticator#authenticate to use a ParameterObject
* SONAR-10598 Redirect user when login is updated and update personal org
* SONAR-10598 Improve update of personal organization key
* SONAR-10598 Improve IT stability related to generation of provider ID
* SONAR-10598 Add USERS#ORGANIZATION_UUID
* SONAR-10598 Replace usage of Organizaions#UserId by Users#OrganizationUuid
Extract hash mechanism into a single class LocalAuthentication
Implements SHA1 (deprecated) and bcrypt hash
Set bcrypt as default
Update the hash of a user during authentication if hash method was SHA1
both when user is created with api/users/create or at first authentication
this feature is controlled by property sonar.organizations.createPersonalOrg
* Settings class becomes abstract as multiple implementations
are used. Can't become an interface for binary
backward-compatibility of API
* tests should use MapSettings, an in-memory implementation
of Settings
* web server uses a thread-specific cache of settings when
processing HTTP requests
* web server does not have a cache of settings during startup,
except for the system settings loaded from sonar.properties
* Compute Engine uses a thread-specific cache of settings when
processing a task. Cache is clear at end of task.
* some useless methods of PersistentSettings are removed