HBCI, Xs2a-Payments, Encryption release

• Feature: SCA exemption support (0-SCA challenges)
• Feature: Payment without (anonymous) or with login into OpenBanking dictated by API flag if FinTech desires user identification
• Feature: HBCI Sandbox server with account information, transactions, payments support
• Feature: Oauth2 OpenID login into FinTech
• Feature: Secure password storage in FinTech-examples, service account support
• Feature: Show consent and payment details in UI
• Feature: Show intermediate payment status in FinTech (Xs2a payment status support)
• Feature: FinTech and OpenBanking automated cookie renewal
• Feature: HBCI Account information, Transaction information, Payments (single)
• Feature: Xs2a Single payment with EMBEDDED and REDIRECT flow
• Feature: Encrypted storage of FinTech request data
• Feature: Protocol (intermediate and at rest) and consent data encryption
• Feature: Private and secret keys encryption and storage using Datasafe
• Feature: PSU login to OpenBanking for better encryption and consent sharing
• Feature: Secure FinTech to OpenBanking calls by request signing (API requests signing)
• Feature: Better FinTech session handling (more secure cookies and XSRF)
• Feature: Session hijacking protection by requiring consent activation by FinTech on user return
• Feature: Updated used dependency of Xs2a adapter to 0.0.9
• Feature: Xs2a transaction list consent request without knowing account resource id
• Feature: Added configuration table to make fields like PSU_ID optional under certain rules/circumstances (mandatory/optional field dynamic override)
• Renamed tables and changes schema to match encryption flow
• Bugfix: SCA selected method and information was not shown
• Bugfix: Avoid retries (Flowable) for unparseable errors
• Bugfix: Removed common issues with the server returning 503 instead of 500