CLI - `-keyring-type secret-service` // Support multiple Boundary server tokens

[daniel-ciaglia]

trafficstars

Describe the bug Using the keyring secret-service stores the token in the wallet but very generic named default with no connection to the server the authentication was done against.

As I have multiple servers, I can not store the token as they are overwritten

To Reproduce Steps to reproduce the behavior:

1. Run boundary authenticate -keyring-type secret-service -addr server1
2. Run boundary authenticate -keyring-type secret-service -addr server2
3. Run boundary connect -addr server1

Error from controller when performing authorize-session action against given target
Error information:
  Kind:                Unauthenticated
  Message:             Unauthenticated, or invalid token.
  Status:              401
  context:             Error from controller when performing authorize-session action against given target

Expected behavior Support multiple server authentication tokens