Goal: 

Until HMS-3843 it was not possible for a user to override an inhibitor detected in a pre-conversion analysis report. With HMS-3843, users can now put environment variables to the rhc-worker-script configuration file and through that override conversion inhibitors. The goal of this ticket is to document for users how they can override a detected inhibitor.

This way of overriding inhibitors is not ideal from the user experience perspecitve because the user is told in the Insights UI to set an environment variable to override an inhibitor which is problematic for two reasons:

1. they need to leave the Insights UI and ssh into each machine on which they want to override an inhibitor
2. instead of setting an env var the usual way in shell, they need to add the env var to an rhc-worker-script config file

Both of the above problems will be resolved by RHELC-1514 and RHINENG-8807. Until then, let's create a knowledge base article explaining the currently only way of overriding inhibitors.

Acceptance Criteria:

• A knew KB article describes how to override an inhibitor - through adding an environment variable to /etc/rhc/workers/rhc-worker-script.yml
• The currently documented known issue about not being able to override an inhibitor in Insights is updated to point to the KB article