Display info about unavailable fields while adding/editing report

[hstastna]

Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=1581817

What:
When choosing Chargeback for Images/Projects/Vms under Configure Report Columns section while adding a new/editing an existing Report under Cloud Intel > Reports > Reports, some of the fields are not available. This is ok but there was a misunderstanding that those fields were missing there. This is why I am adding note about which fields are not supported to the Report editing screen.

Steps to reproduce:

1. Go to Cloud Intel > Reports > Reports accordion
2. In toolbar, choose Configuration > Add a new Report (or you can also edit an existing report)
3. Under Configure Report Columns, for Base the report on choose one of Chargeback for Images/Projects/Vms
   => some of the fields are not available, for example Cpu Cores Allocated Metric for Chargeback for Fms (Carefully! They are not missing!)

Before:
Choosing Chargeback for Images while adding/editing report:

Choosing Chargeback for Projects:

Choosing Chargeback for Vms:

After:
Choosing Chargeback for Images while adding/editing report:

Choosing Chargeback for Projects:

Choosing Chargeback for Vms:

[hstastna]

@miq-bot add_label bug, hammer/yes

[lpichler]

Overall looks good 👍 thanks @hstastna

[mzazrivec]

Using string arithmetics for gettext strings is generally a bad idea. It makes the work of translators more difficult, plus the resulting translated string will not always make sense.

[hstastna]

Hmm, that is interesting because I was told to do so in some other PR. So what is your suggestion instead of this? What is the best? Thank you.

[mzazrivec]

Well, you need to put the static parts of the string together in one place (in this case, probably the controller) and substitute %{rep_base} here (that's the only dynamic part, correct?)

[miq-bot]

Checked commits hstastna/manageiq-ui-classic@01d2a9a~...bc17b0f with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
4 files checked, 1 offense detected

**

• 💣 💥 🔥 🚒 - Linter/Haml - Linter::Haml STDERR:

warning: parser/current is loading parser/ruby23, which recognizes
warning: 2.3.6-compliant syntax, but you are running 2.3.3.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.