Licensing key username constraints too restrictive

[jimfim]

Describe the bug License Key username matching is too restrictive. I would like to be able to use k9salpha on whatever machine I'm logged into

To Reproduce My corporate UserName includes the domain name as part of my user so so acme\jimjim I primarily use Windows but I rely on WSL heavily for development, by matching my key to my corperate domain name It means I can't use k9salpha via WSL on the exact same machine or on my laptop

Expected behavior Once I have the key I should be allowed use k9salpha where ever I like. This is common practice with many applications. tying my key to the user and machine name is too restrictive and hampers the usefulness of this tool

Screenshots

jimjim@JIMJIM-PC  ~  >  whoami
acme\jimjim
jimjim@JIMJIM-PC  ~  >  wsl
$ whoami
jimjim
$ k9salpha
 ____  __.________          _
|    |/ _/   __   \______  / /
|      < \____    /  __/ \/ /
|    |  \   /    /\___\    /
|____|__ \ /____//____ >_/_\
        \/            \/

Boom!! unauthorized license [1] "ACME\\jimjim":"jimjim".

Versions (please complete the following information):

• OS: WIN10 with WSL
• K9s⍺: v1.0.0-rc.2

 ____  __.________          _
|    |/ _/   __   \______  / /
|      < \____    /  __/ \/ /
|    |  \   /    /\___\    /
|____|__ \ /____//____ >_/_\
        \/            \/

Version:    v1.0.0-rc.2
Commit:     a6edef9c974f30946b720ee9cf6ee5e063605ee3
Date:       2021-04-28T16:09:43Z