TAR and ZIP files must be able to use data reference names without special treatment

[de-jcup]

Situation

With #1098 we introduced the data configuration element which source an binary configuration elements have unique names which can be referenced.

Currently following is validated:

• min length
• max length
• uniqueness inside model

But the names can be everything.

While writing documentation about data in

• Explain data-section parts inside documentation #1218
• Define and document the TAR and zip structure for data sections #1163
  it became clear that when the names are used for tar and zip structures they
  must be valid file pathes as well.

But currently they aren't! If we would use "~/" or "../.../" this would be very problematic...

Wanted

TAR and ZIP files must be able to use always the unique data reference names
without any encoding or escaping mechanism.

Solution

We simply add another validation to the sechub configuration model:
We only accept reference names which do contain a-z, 0-9, - or _