Device redirection token (JWT) includes a hardcoded empty string value for tenantId

[bgmckown]

Describe the bug 🪲
The JWT for device authentication (redirection) currently includes a field for tenantId but is hardcoded to an empty string.

If an implementation of the toolkit is using the tenantId value to manage multi-tenancy, will this hardcoded line in the JWT signature creation method create any issues with devices that are associated to a tenantId?

To Reproduce 🪜
Steps to reproduce the behavior:

1. Go to /src/routes/auth/signature.ts#L14 (currently in the main branch)

Expected behavior

• If the tenantId field is to be used in the JWT, then it should be set to the actual tenantId associated with the device in the toolkit database.
• Consider removing the tenantId field from the JWT signature if there isn't a multi-tenancy need for it.

Screenshots 🖼️
n/a

AMT Device (please complete the following information): 🖥️
n/a

Service Deployment (please complete the following information): ⛈️
present in MPS source code for version 2.26.0