Minimize use of eval() in JavaScript due to emerging Content-Security-Context guidelines

[TheWitness]

Describe the bug
Browsers are not requiring Content-Security-Contexts in the browsers header in meta tags or, by default, content is not viewable.

Expected behavior
Cacti should refrain from dependency of eval() within the code, as well as using inline JavaScript.

Inline JavaScript is also problematic to many security professionals and should also be avoided. However, Cacti 1.2.x leverages in inline JavaScript extensively, though evals() are only used in select areas. Therefore, inline JavaScript removal will have to wait for Cacti 1.3 before being extracted.

[TheWitness]

Noting additionally that the following are using eval:

• most cacti themes
• jquery.timepicker.js
• jquery.zoom.js
• jquery.metadata.js - which is not in use and should be removed from the Cacti distribution