Restructure projects to introduce ScriptSharp translation

[andry-tino]

So far a separation has been made:

• Rosetta C# translation
• Rosetta ScriptSharp definition generation

Rosetta must be able to translate generic C# code and C# code which has been written specifically for ScriptSharp. Thus the separation must be:

• Rosetta C# translation
• Rosetta C# ScriptSharp translation
• Rosetta ScriptSharp definition generation

In order to do that a new project must be introduced: ScriptSharp. Components need to be re-wired and tests need to be rewired as well.

Projects

Changes to do:

• Rename ScriptSharpDefinition into ScriptSharp.Definition
• Rename ScriptSharpDefinitionRunner into ScriptSharp.Definition.Runner
• Rename ScriptSharpDefinitionBuildTask into ScriptSharp.Definition.BuildTask
• Create project ScriptSharp

In tests:

• Rename ScriptSharpDefinition.ASTWalker.Renderings into ScriptSharp.Definition.ASTWalker.Renderings
• Rename ScriptSharpDefinition.ASTWalker.Renderings.Data into ScriptSharp.Definition.ASTWalker.Renderings.Data
• Rename ScriptSharpDefinition.ASTWalker.Factories.UnitTests into ScriptSharp.Definition.ASTWalker.Factories.UnitTests
• Rename ScriptSharpDefinition.ASTWalker.UnitTests into ScriptSharp.Definition.ASTWalker.UnitTests
• Rename ScriptSharpDefinition.BuildTask.Example into ScriptSharp.Definition.BuildTask.Example

Rearrangement

Components to be rearranged:

• Move ScriptNamespaceBasedASTTransformer into ScriptSharp project
• Move all helpers from ScriptSharpDefinition into ScriptSharp

Rearrange tests accordingly to new structure in source.

Final notes

Rearrangement is only at filesystem level in the file organization. Namespaces in files are fine.

[andry-tino]

This effort is preparatory for #29.