add prefix/suffix if ent reserved words are detected

[thmeitz]

Actual
A DB has a clients table that collides with ent.Client and a subsequent change to the ent.Schema is necessary to fix the error.

Suggestion
When importing an existing database with entimport, there should be a prefix (or suffix) for the generated methods.
In the configuration for entimport there should be an option to specify the prefix.

Example
prefix: legacy
table: clients
Result: LegacyClient

[zeevmoney]

Hi @thmeitz,

I actually wanted to optionally prefix the database "schema" name, but I also like this idea of custom prefix.
Suggested it in here: #29
I will take your idea into consideration when implementing the feature and add it to the relevant roadmap section. If you want, contributions are always welcome, I'm in the discord, and happy to provide any support.