Fortress GB configuration

General Principle: Fortress GB generates the barcodes and prints the Season Ticket cards

this has some impacts:

1. Seatmap inside SecuTix and Fortress Gb has to se synchronized:
   1. same area codes + block codes + row + seat number
   2. SecuTix outer perimiter entrance codes must match with Fortress gates' codes
   3. SecuTix inner perimiter entrance codes must match with Fortress turnstyles' codes
2. Product + Tarriff + XXX codes have to match between SecuTix and Fortress GB
3. When a ticket is created, Fortress generates
   1. a standard barcode, which is stored in SecuTix ticket's barcode
   2. an Adult barcode, stored in external manager movement XXX, which is then available on ticket editor with field named ZZZ_???
   3. a concession barcode, stored in external manager movement YYY, which is then available on ticket editor with field named ZZZ_???
   4. a ticket identifier,stored in external manager movement TTT, which is then available on ticket editor with field named ZZZ_???