The introduction of the in-memory cache for application settings had a
side effect of making it harder to invalidate changes when the settings
occur. We now bypass the cache because it's possible the admin enabled
the usage ping, and we don't want to annoy the user again if they
already set the value.

To avoid causing significant load on the system, we add an extra check
to ensure the user is an admin. and we don't want to annoy the user
again if they already set the value. This is a bit of hack, but the
alternative would be to put in a more complex cache invalidation
step. Since this call only gets called in the uncommon situation where
the user is an admin and the only user in the instance, this shouldn't
cause too much load on the system.

Disabled password authentication for the users registered using
omniauth-ultraauth strategy

Signed-off-by: Utkarsh Gupta <guptautkarsh2102@gmail.com>

Udpated user_edit_profile_spec with time preferences

Minor update form fields

Removed the conditions added to
Project.with_feature_available_for_user, and moved to the
IssuableFinder. Now, we ensure that, in the projects retrieved
in the Finder, the user has enough access for the feature.

Model.new.attributes now also returns encrypted attributes.

- Update PO file

It's not needed anymore as we've replaced boolean `support_bot` with
enum `bot_type`.

Add columns to store project creation settings

Add project creation level column in groups
 and default project creation column in application settings

Remove obsolete line from schema

Update migration with project_creation_level column existence check

Rename migrations to avoid conflicts

Update migration methods

Update migration method

Truncate existing users names which exceed 128 characters
Include test for truncating users names