Re-org new Razor12 classes to have new APIs, and ensure old ones don't

[iJungleboy]

I'm submitting a ...
[x] Refactor request

...about
[x] Razor templating
[x] Custom C# APIs

Current behavior

2sxc 12 introduces a few new APIs like Settings, Resources and Convert. This could cause trouble in old code, which may have used terms like Convert already. For example, old code could have Convert.ToInt32 which is a System.Convert object.

Expected behavior

New razor inheriting from Custom.Hybrid.Razor12 or Custom.Dnn.Razor12 should get these new commands, older base classes should not.

Why change the behavior?

It's too risky that we would break very old code which already used terms like Convert or Settings.

Your environment

• 2sxc version(s): 12.04