JDBCSourceAdapter2 and getSubjectIdentifierAttributesAll breaks subject cache

The JDBCSourceAdapter2 falls back to the JDBCSourceAdapter implementation of getSubjectIdentifierAttributesAll, which uses config parameters that aren't loaded by JDBCSourceAdapter2, resulting in getSubjectIdentifierAttributesAll to always only return the subject ID. This causes problems in the subject cache leading to errors like:

In subject source: personSource the identifier: 'xxxx' can find subject: 'yyyy', but the attribute for that identifier is not configured in the subject source. In order for caching to be effective, please list all identifier attributes in the subject source. You can configure to suppress this log message in subject config.

For the JDBCSourceAdapter2, there is no way for this to be accomplished with the current code. Implementing getSubjectIdentifierAttributesAll for the jdbc2 adapter is easy, so I'll implement and submit a PR on gitlab.