Move parts of RamModelUtil to model project

[Matthias Schoettle]

The class RamModelUtils in ca.mcgill.ram.utils contains a lot of methods related to RAM model utilities that are not related to the GUI at all.

Create a class RamModelUtil in package ca.mcgill.cs.sel.ram.util and move non-GUI related methods there.

This class can then also be extended with functionality for message view helper methods etc.

See also issue #67.

[Matthias Schoettle]

Issue #67 introduced RAMModelUtil, which should be used for this issue as well.

[Matthias Schoettle]

References issue #68: Moved String utility methods to StringUtil in commons.

→ <<cset eed75c9e7cbc>>

[Matthias Schoettle]

References issue #68: Moved isUniqueName to RAMModelUtil.

→ <<cset f71c69523237>>

[Matthias Schoettle]

References issue #68: Moved createAspect, layout and default types to RAMModelUtil. This includes the private method getTypeInstance.

→ <<cset 7156035c8226>>

[Matthias Schoettle]

Resolved issue #68: Moved getPrimitiveTypes to RAMModelUtil. Methods related to GUI tasks (getting a type by name) are kept in the old RamModelUtils for now.

→ <<cset 6e0183c33cf5>>