Aha Configuration: use the custom terminology from the topmost Product Line

We use Aha's terminology option to remap several Aha terms to the words we use in our software lifecycle (thank you for that!). For instance, epics are re-labeled "initiatives", features are "epics", and requirements are "stories".

However, the default Aha terms are used in all Aha configuration screens. This causes cognitive dissonance: when I see the term Epic in Custom Layout settings, I have to remember that it means "initiatives" everywhere else.

Please use the custom terms we've set so that it's less confusing to manage. To be clear, I don't expect this would carry over to Support articles.