[BUG] Restore Config Fails Without "admin" User

[jdonextgen]

Describe the bug
When the Server Restore Config fails, we are shown an error message that says "Error restoring server configuration." but parts of the Server Restore Config did successfully restore. The error message seems to imply that the entire restore failed. For a specific part of the restore, if it fails, you may get an error message like the following, "Error restoring plugin properties.". It'd be more helpful if the error message described more details on what and why it failed, e.g. plugin name and what specific thing failed.

To Reproduce
Setup steps (if required).

1. Install Connect and the Role-Based Access Control extension
2. Download the attached ServerConfig, this backup should have 2 test channels, an environment and server name, and 3 roles (Administrator, Alerts Role, and Channels Role). (see ticket for attached file)

Steps to reproduce the behavior:

1. Start MC, overwrite the default “admin” user and change to “tester” ( or add “tester” user and remove “admin” user)
2. Check Roles, verify “tester” with Administrator role
3. Log out and log in as “tester”
4. Go to Settings > Server > Restore from the provided config

Expected behavior
Should still restore all of the configuration except for the user roles; the server log will indicate which specific part of the configuration restore errored while the pop-up dialog box will notify the user of a partial configuration restore and point the user to the server log for more information. The Server Log will also include more detailed error message about which specific part of the restore failed.

Actual behavior
The restore of the configuration happens for all parts except for the user roles but the error messages we get are ambiguous.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• OS: [e.g. Linux (CentOS), Windows 10, MacOS]
• Java Distribution/Version [e.g. OpenJDK 11, Java 8 (201)]
• Connect Version [e.g. 3.8.0] 4.1.1, 4.0.0

Workaround(s)
Keep admin user and restore config

Additional context
Add any other context about the problem here.