When enum types is set as `goEnumAsSet` by user, we need to add
`goEnumAsEnum` also in order to correctly handle non bit fields enums.
This should be done at the very beginning, upon CLO handling, otherwise
some enums are generated as integer constants.
These changes are:
1. Added line break to last line of generated files.
2. Removed unused field `FEnumImpl` from `TGirConsoleConverter`.
3. Moved command line from .lpi to .lps as this depends on the path
of the user debugging the program.
Added a new command line option (CLO) `-e/--declare-enums-as` that
selects the way how to define C enums and bit fields.
Added support for 4 options and a 5th to be implemented later.
1. `IntConst`: No type, just use integer non typed constants. This was
already implemented, but not easily selected at CLI.
2. `TypedIntConst`: Use non strict type aliases and typed constants.
This was already implemented, selected by default in the code.
3. `IntAliasConst`: Use strict type aliases and non typed constants.
This was newly added.
4. `Enum`: Use Pascal enumeration type for both C enums and bit fields.
This was newly added.
5. `Set`: Use Pascal enumeration type for both C enums and Pascal sets
for bit fields. This is not yet added.
As the directories search list is not sorted, FPC implementation of
`TStringList` ignores the `dupIgnore` option and thus leads to having
the same entry multiple times in the list.
We forbid this manually in order to avoid searching multiple times for
the same file in the very same directory.
We also add more default search paths (Debian based).
The order of folders where to search for included files should be
related to user preference as follows:
1. directory where the input is located,
2. directories supplied by user at command line in the order they were
passed,
3. default system directories, where distributions used to put them.
This way, user can easily override files in the default system
directories without the need to have write access to such folder, as in
most Unix systems this will require root access.
Also, one expects, that if copy of an included file is placed in the
same directory as the input one, then this copy should be used.
This makes sens, because people generally work on the same directory,
and will consider their local work copy the preferred one to be used.
