Draft: Add storage configuration respecting user certificates with VO

Merging, splitting, and cleaning took some time, but in principle all was tested few days ago.

There is a difficulty in the way FTS works with proxy in the case of VO. FTS has "ctao" VO built-in now.

There is also a fundamental difference between VO treatment by Rucio vs RSEs: user may be member of VO but proxy have no VO. In rucio it's not possible.

Changes:

• add voms-compatible xrootd
  • add own xrootd container with voms libraries
  • configure test storages with own xrootd container to give access to a ctao.dpps.test path RO
  • configure single account for use by daemons
• all existing tests will use by default x509 proxy with VO extension, using the same path as previously user-bound path
• add more tests with unauthorized certificates - without VO