Remove "Runtime" from all namespaces.

[codemzs]

Partially fixes #1697 by removing "Runtime" from all namespaces and that is it, no moving classes to other namespaces.

[TomFinley]

@codemzs out of curiosity what is your plan w.r.t. namespace sorting and the like? Not do it, other?

[codemzs]

@TomFinley I plan to automate that using a script in a separate change but if you insist we do it in this change that is also fine by me but please let me know.

[TomFinley]

No, I do not insist, just wanted to know plan is all, thanks.

[TomFinley]

Great, thanks @codemzs.

[TomFinley]

Interesting, good one, I wonder if we should have some mechanism to check for this sort of thing, right now it's purely manual.

[justinormont]

I don't think there's a better way for this PR (hard to slice this PR in to parts), but w/ 923 files changed, the GitHub web GUI is pretty inadequate for the task.

If anyone is tired of opening each "Load diff" for each file, you can put this your browser's JS console to open all:

[...document.getElementsByTagName('button')].filter(a=>a.innerText.trim() === 'Load diff').forEach(a=>a.click())

One less tedious step :)

[justinormont]

fyi -- so anyone else reading this doesn't go and check, GetApiName() seems to handle "":

machinelearning/src/Microsoft.ML.Legacy/Runtime/Internal/Tools/GeneratedClasses.cs

Lines 27 to 38 in a8b844c

	public string GetApiName(Type type, string rootNamespace)
	{
	string apiName = "";
	if (!_typesSymbolTable.TryGetValue(type.FullName, out ApiClass apiClass))
	apiName = GenerateIntenalName(type, rootNamespace);
	else
	apiName = apiClass.NewName;
	if (!string.IsNullOrEmpty(rootNamespace)&& apiName.StartsWith(rootNamespace))
	return apiName.Substring(rootNamespace.Length + 1);
	else return apiName;
	}

[justinormont]

@ganik, @montebhoover: I assume NimbusML isn't taking in the TimesSeries work yet. If so, the renaming of the EntryPoint might affect NimbusML.

[justinormont]

LGTM -- can you put in an issue to also fix up example code to remove Runtime?

In the future, we may want to wrap a unit test around a duplicate of all of our example code to ensure it stays in sync.

[codemzs]

@justinormont Good idea, will do that. Thanks for reviewing!
@TomFinley thanks for reviewing.