v2 to v3 update hook conflicts with some configuration deployment workflows

Problem/Motivation

Reported by @cilefen.

>  [notice] Update started: editoria11y_update_9012
>  [error]  'view' entity with ID 'ed11y_action' already exists. 
>  [error]  Update failed: editoria11y_update_9012 

There is a potential `drush updb` vs `drush ci` order of operations problem, because the 2->3 update hook assumes it will see 2.x config. Updating local, committing that config, then running updb on prod confuses the update hook, whereas updating in production and then running config-import tries to restore un-updated config.

This only affects certain tooling workflows.

Fix will be to modify update hook 9012 to detect intermediate states and disambiguate, and to document the process.