fix: Don't encode @ in project name

[dominik003]

T4C uses an intersting encoding for project names described in more detail here. Since our projects shouldn't use any special characters anyways, we can avoid reproducing their encoding by simply adding characters to the safe list if encountering a project with such a character.

Resolves #142

[MoritzWeber0]

In the references article, it is stated:

While URIs are limited to a subset of the US-ASCII character set (characters outside that set must be mapped to octets according to some unspecified character encoding, then percent-encoded), IRIs may additionally contain most characters from the Universal Character Set (Unicode/ISO 10646)

Therefore, we can just take all ISO_10646 characters and pass them as safe chars.

Since our projects shouldn't use any special characters anyways, we can avoid reproducing their encoding by simply adding characters to the safe list if encountering a project with such a character.

They SHOULDN'T in theory, but they do in practise. Therefore, I would prefer a more stable solution.

[dominik003]

In the references article, it is stated:

While URIs are limited to a subset of the US-ASCII character set (characters outside that set must be mapped to octets according to some unspecified character encoding, then percent-encoded), IRIs may additionally contain most characters from the Universal Character Set (Unicode/ISO 10646)

Therefore, we can just take all ISO_10646 characters and pass them as safe chars.

Since our projects shouldn't use any special characters anyways, we can avoid reproducing their encoding by simply adding characters to the safe list if encountering a project with such a character.

They SHOULDN'T in theory, but they do in practise. Therefore, I would prefer a more stable solution.

Seems like I put the wrong link in there (not the actual link to the eclipse page which is the following: URI (EMF Documentation)). There it is stated:

This implementation uses Java's Unicode char and String representations, and makes no attempt to encode characters 0xA0 and above. Characters in the range 0x80-0x9F are still escaped. In this respect, EMF's notion of a URI is actually more like an IRI (Internationalized Resource Identifier), for which an RFC is now in draft form.

So as far as I see there is not just a clear set of characters we can ignore when quoting or how would you do that?

[MoritzWeber0]

Looks good for now, however we should investigate it in more detail: #229