WWSympa: Bug: Accessing to /sympa/help may crash

Update test suite

  - Renamed some test files for consistency.
  - All tests under t/ were made available on Travis-CI & GitLab CI.

Data source: File: gecos was ignored

Unable to sort column in subscriber list (#866)

Adding tests for #868

Addition to #840

Unreasonable error message to notify broken signature with PGP/MIME messages

Urlize mode bug fixes

Fixed by correcting query.

Unreasonable error message to notify broken signature in the message, if the messages signed with PGP/MIME was posted.

Deprecate one time ticket (2) (#156)

In some cases, a message will start with a multipart/related including a multipart/alternative; In that case, with the current code the multipart/related was urlized as a 'msg.0.bin' attachment, which was wrong.
Fixing this behaviour by:
1- allowing to go down two levels of multiparts
2- preventing any urlization if the part is not included in a 'multipart/mixed' parent to prevent urlizing the content of multipart/related or multipart/alternative.

Deprecate one time ticket (1) (#156)

Prevent welcome emails on import with --quiet.

Following suggestion by reviewer @ikedas: Replacing 'get()' by 'mime_attr()' and, therefore, a regular expression by 'eq'.

family_signoff action no longer does use one-time ticket.

Including stub to libraries, so Constants.pm is found. Adding Sympa constants because most of them are needed when using
 Sympa libraries. Specifying the sources 'default' directory for 'DEFAULTDIR' constant to allow access to distributed templates.

  - t/Message.t,
  - t/samples/ contains six different messages for testing urlize,
  - t/data/ now contains a test list configuration file.

1- message text was treated as attachment and remained on the server as either "msg.0.bin" or "msg.0.txt" files. Fixed by testing the part type before urlizing it.
2- some special characters in message id led to the attachment to be considered missing by Sympa.

I had to refactor the code a bit to allow urlizing of nested multiparts.

The detail of urlization treatment is as follows:

1- any multipart/mixed message part will be analyzed to look for urlizable parts,
2- any mulitpart/related message part will be be analyzed to look for multiârt/mixed sub parts,
3- within the multipart/mixed parts, any text/* part whose "Content-Disposition" header is not "attachment" and has a correct Content-Type.charset value is kept untouched,
4- any other subpart is kept on the server an replaced by a download link.

Additional fix for #841