Update utils.py

[Nazarinh0]

For cyrillic names on social accounts - the encode and decode operations result in replacing all chars with empty string. And later in try-except block clean_username does not raise a ValidationError, so empty string username is considered valid. As a result, "user" is returned at first iteration and other txts are not even being processed. For example, I have last name, email, username on my social account, which is in latin alphabet and would be suitable for use as a username, I still will be called "user" because of cyrillic name. This issue may affect all non-latin names or last names including russian, chinese, arabic and so on.

Submitting Pull Requests

General

• Make sure you use semantic commit messages.
  Examples: "fix(google): Fixed foobar bug", "feat(accounts): Added foobar feature".
• All Python code must formatted using Black, and clean from pep8 and isort issues.
• JavaScript code should adhere to StandardJS.
• If your changes are significant, please update ChangeLog.rst.
• If your change is substantial, feel free to add yourself to AUTHORS.

Provider Specifics

In case you add a new provider:

• Make sure unit tests are available.
• Add an entry of your provider in test_settings.py::INSTALLED_APPS and docs/installation.rst::INSTALLED_APPS.
• Add documentation to docs/providers/<provider name>.rst and docs/providers/index.rst Provider Specifics toctree.
• Add an entry to the list of supported providers over at docs/overview.rst.

[coveralls]

coverage: 95.895% (+0.001%) from 95.894%
when pulling 47167eb on Nazarinh0:patch-2
into bd7b69f on pennersr:main.