user-jwts should just create the UserSecretsId if not found

[timheuer]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When using dotnet user-jwts create if there is no UserSecretsId it will fail saying one is not found. We should either:

• (Preferred) Generate the UserSecretsId for the user...this is non-impacting for the code and creates a delighter to complete the task fully that I asked it to do (show in output 'user secrets not found, generated [guid]' before adding the newly created token
• Clarify what to do in the event UserSecretsId is not there (IMO, not an awesome experience to use a separate tool)

#41956 (comment)

Expected Behavior

The token is just created for me, doing what is needed to create the secrets/file association if not found.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

[adityamandaleeka]

@captainsafia, assigning this to you since it's follow-up from the user-jwts work.