REFACTORED ra-scoped-reset +  CSS/ASSET API CHANGE (w/ backcompat)

The 'ra-scoped-reset' CSS has been rewritten from scratch and now ONLY
resets the global changes made by the ExtJS CSS. This was done
surgerically, tag by tag, rule by rule by comparing ext-all.css to
built-in CSS that ships with Firefox. This probably should have been
done in the begining than trying to apply a general css reset blindly.
But, it has been done now, and now 'ra-scoped-reset' no longer applies
any additional style defaults beyond undoing what ExtJS did...

The need for sane CSS style defaults are a separate issue from the
scoped reset need to escape from ExtJS CSS within nested html content
(i.e. templates) and has thus been factored out of ra-scoped-reset.

The base styles (which came mostly from bootstrap) which were in
ra-scoped-reset are now in their own, optional scoped css asset 'ra-doc'
(which replaces older/depricated CSS of the same class name).

TC Access class API:

The Template::Controller::Access class API has also been expanded with a
new method 'template_css_class' which is now called for each template
when rendering. If this method returns a string value (instead of
false/undef), it is added to the class of the div wrapper (along side
'ra-template').

There is also a new Access class attr 'default_template_css_class' which
is returned for all templates if specified in the base Access class
(although, the template_css_class method can be overridden in custom
Access classes for fine-grained per-template control). Currently, the
default value of 'default_template_css_class' is set to the new scoped
CSS class 'ra-doc', as described above.

The net net effect of this is that by default, every template is
rendered within a 'ra-doc' div, and also still nested within the
'ra-scoped-reset' div, which combined yield the same effective styles in
rendered templates as before, when they were all stuffed within
'ra-scoped-reset' ...

However, with this change, the user app can now easily customize or
change to use a different base CSS for templates, or none at all (by
setting default_template_css_class => undef in 'access_params' under the
'Controller::RapidApp::Template' config). This allows the best of both
worlds: out-of-the-box styles are still pretty, but custom apps with
custom CSS can easily escape the defaults without a lot of fuss.