Remove redundant calls for mootools

As most of the javascripts are now based on jQuery some calls to load mootools framework are redundant.
This is a response to #4473
This PR removes it from 
> formvalidate  https://github.com/joomla/joomla-cms/blob/staging/libraries/cms/html/behavior.php#L151
> combobox https://github.com/joomla/joomla-cms/blob/staging/libraries/cms/html/behavior.php#L215
> tooltip https://github.com/joomla/joomla-cms/blob/staging/libraries/cms/html/behavior.php#L257
> modal https://github.com/joomla/joomla-cms/blob/staging/libraries/cms/html/behavior.php#L326
> noframes https://github.com/joomla/joomla-cms/blob/staging/libraries/cms/html/behavior.php#L701

The only case I left the moo tools framework is for tree.

B/C
Shouldn’t break something, as the scripts are NOT moo tools dependent. 

Test
Try different navigation on a site (admin will be easier) and check that form validate, compobox, tooltip, modal and noframes still function as usual. Please check 3PD code with this, let’s NOT break things here!!!

EDIT
Except libraries/joomla/cms/html/behavior.php 

I found out that toolbar is always loading mootools, for no particular reason so removed it from the files confirm, standard, help in libraries/joomla/cms/toolbar/button

Also almost all backend views have a basic check for the form where the code expects mootools 
```
document.id('banner-form’)
```
This can be done also with vanilla ```document.getElementById('banner-form’)```
So most of the changes are document.id -> document.getElementById

Thanks @fedik for the heads up!!!



maybe better change the order to be logical? 
(the core first, and all else go after)