Device access checks and metadata middleware

[j-mai]

Currently, when we are adding the device metadata, we require that the attributes from the token parsed by bascule implements the RawAttributes interface in order to copy all of the claims into the device metadata:

talaria/middleware.go

Line 26 in ee5fb72

if tokenAttributes, ok := auth.Token.Attributes().(RawAttributes); ok {

If it doesn't implement the RawAttributes interface, we only copy the partner-id and trust claims: https://github.com/xmidt-org/talaria/blob/ee5fb72dd3f6a2d3b8a86a770e7354d683cf315f/middleware.go#L29-#L36

This is currently fine, since our device access check mainly only uses partner-id. However, this can be problematic if we decide to add checks to the deviceAccessChecks section of the config that are not partner-id or trust, and device access check will fail. A possible solution is to instead get all of the claims that are described by the deviceCredentialPath in all of the configured checks that are listed in the config:

talaria/talaria.yaml

Line 358 in ee5fb72

# # deviceCredentialPath: partner-ids