Use local assets for code coverage report for offline usage

[PhilippSalvisberg]

The ut_coverage_html_reporter has an optional parameter a_html_report_assets_path to pass the URL prefix for the following assets required by the code coverage report:

• application.js
• application.css
• favicon_green.png
• favicon_yellow.png
• favicon_red.png
• loading.gif
• magnify.png
• colorbox/border.png
• colorbox/controls.png
• colorbox/loading.gif
• colorbox/loading_background.png
• images/ui-bg_flat_0_aaaaaa_40x100.png
• images/ui-bg_flat_75_ffffff_40x100.png
• images/ui-bg_glass_55_fbf9ee_1x400.png
• images/ui-bg_glass_65_ffffff_1x400.png
• images/ui-bg_glass_75_dadada_1x400.png
• images/ui-bg_glass_75_e6e6e6_1x400.png
• images/ui-bg_glass_95_fef1ec_1x400.png
• images/ui-bg_highlight-soft_75_cccccc_1x100.png
• images/ui-icons_222222_256x240.png
• images/ui-icons_2e83ff_256x240.png
• images/ui-icons_454545_256x240.png
• images/ui-icons_888888_256x240.png
• images/ui-icons_cd0a0a_256x240.png

The default value for the report asset path is https://utplsql.github.io/utPLSQL-coverage-html/assets. This means that the code coverage report works only, if the default browser has access to the internet.

Instead of downloading the assets from the internet, they should be included in the SQL Developer extension. The resources (assets) are stored in this repo. These assets can be copied into the same temporary directory as the HTML file.

[PhilippSalvisberg]

The parameter a_html_report_assets_path has been added on March, 6 2017. So the first version with this parameter was v3.0.0-beta. Hence, no version specific handling is necessary.