[PRD-5086] - When auto-submit is off, the report parameter/prompt panel flashes/glass pane appears.

Made changes so that the glass pane is only shown with a dark background when the report is being updated (this is the most time-taking process).
When the glass pane is shown, but only the prompt is being refreshed, it is shown transparent, achieving a less disruptive user experience.

The incremental recreation of each of the prompt's CDF controls still significantly disrupts the user experience. It looks like a slide-in effect.

* Summarising, I made two changes:
** replaced all explicit calls to show/hide the glass pane's dojo element with calls to central functions having the same code; this change is conservative of the original behaviour - a refactoring;
** then (a behaviour changing change), the new show/hide methods add logic that additionally controls the glass pane's transparency.

Detailing the changes:
* In reportviewer-prompt.js
** Created two methods in the report-viewer prompt showGlassPane and hideGlassPane whose implementation calls show/hide on the dojo element.
** Replaced all existing calls to show/hide the dojo element with calls to showGlassPane and hideGlassPane.
** Moved the call to showGlassPane in getParameterDefinition to fetchParameterDefinition.
*** This location is more central: it accounts for other scenarios where fetchParameterDefinition is being called directly (in reportViewer.js), and thus required additional explicit calls to showGlassPane.
* In reportviewer.js
** In the same spirit of other existing code, the default prompt showGlassPane and hideGlassPane implementations are overridden with view-specific implementations. These implementations use details only known by the view (whether the report content is loading as well or not) to control the transparency of the glass pane, when showing/hiding.
* A new method was added, "reportContentUpdating", which uses the already existing "_updateReportTimeout" variable.
* Taking advantage that fetchParameterDefinition already calls showGlassPane, the existing call in _updateReportContent can be moved to the only branch of code which doesn't issue it: the _updateReportContentCore method. It is placed right after the update to "_updateReportTimeout" variable, so that showGlassPane can know that the glass pane must not be transparent.
[BISERVER-10656] - Upgrade Dojo usage to 1.9
* A bug was occurring when a report was output with the format "HTML (single page)" and had no content.
* The dojo API dojo.dnd.getViewport() does not exist anymore in 1.9
Merge pull request #86 from webdetails/BISERVER-10656

[BISERVER-10656] - Upgrade Dojo usage to 1.9
Merge pull request #85 from webdetails/PRD-5086

[PRD-5086] - When auto-submit is off, the report parameter/prompt panel flashes/glass pane appears.
[PRD-5097] Previous/Next/Current page controls don't work. First page is
always returned.
Merge pull request #87 from e-cuellar/master

[PRD-5097] Previous/Next/Current page controls don't work. First page is always returned.
[PRD-5098] - Report having a textbox parameter, and auto-submit off, submits multiple times, and finally stops.
Merge pull request #88 from webdetails/PRD-5098

[PRD-5098] - Report having a textbox parameter, and auto-submit off, sub...
[MOBILE-293] -- Forced body of report viewer to always take up visible area so that the content, larger than the view area, would be able to scroll
Merge pull request #89 from krivera-pentaho/dev

[MOBILE-293] -- Forced body of report viewer to always take up visible a...