Not prepending 'API-Key' string in front of token of auth-header.

[mmzx]

This is a piece of a set of modifications that would allow the front-end to use a bearer token to be passed.

The reason for this change

In particular, one cannot assume, in general, that the Authorization header always gets created using an API-Key. This updates puts the caller (client/user) to be responsible regarding the type of token to be used (API-key or Bearer) when performing authentication against the mining backend.

The change is required to be in effect, potentially, by the time when API-Key will not be supported any more. This also includes the potential change when the mining frontend will stop using API-Key as a means of authentication for custom dashboards.

Future task(s)

• Release a new version PyLana which is potentially backward compatible (otherwise use version constraints on the end-user side)
• Have PyLana package creation part of CI pipeline
• Uploading the created package to PiPy, so pip can install it.
• In case we want to avoid creating a package, PyLana shall be incorporated in some ways into the dashboard_components repository.
• Use a sum-type to distinguish parsed authorization header values.

[jon-ber]

The edited function would now return {'Authorization': ''} if there is a token passed without "API" or "Bearer" at the start.
Shouldn’t the unmodified token be returned?

[jon-ber]

With the additions of the check for the string length and the removal of the f-string it looks good to me.