Upgrade Assistant surfaces confusing error state for deprecation logging toggle

[cjcenizal]

During a discussion with @LeeDr (#70071 (review)), we discovered that there's a UX bug when the deprecation logging toggle gets back an error after sending its request. The UX is currently designed like this:

1. User clicks toggle
2. Toggle flips state (on to off or off to on)
3. Toggle becomes disabled
4. API request is sent
5. API request resolves successfully and toggle is enabled

Here's how it looks:

However, if the API request resolves with an error, the toggle is stuck in an incorrect state ("on" when it's really "off", or vice versa), and it remains disabled so you can't try clicking it again.

One solution could look like this:

• Show a spinner and "Updating" message when the toggle is clicked.
• If the current state can't be retrieved, replace the toggle with a "Reload" button and a "Can't load deprecation logging information" error message.

[LeeDr]

Agreed. The general flow for clicking a toggle button in Kibana which does a request to Elasticsearch should be to;

1. disable the toggle
2. change state only if the response confirms the request
3. re-enable the toggle