show api keys with deprecated flag

[stylessh]

What kind of change does this PR introduce?

A lot of users still use Anon and Service Role key, they find it difficult to get those while developing with the CLI as they expect to see them in the supabase status command.

e.g 2231, 4211

What is the current behavior?

The CLI skips the deprecated fields instead of showing a tag.

What is the new behavior?

The CLI shows the keys with a soon deprecating tag.

[coveralls]

Pull Request Test Coverage Report for Build 18668903542

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 1 of 9 (11.11%) changed or added relevant lines in 3 files are covered.
• 5 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.08%) to 54.524%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
internal/status/status.go	1	3	33.33%
cmd/root.go	0	3	0.0%
internal/utils/colors.go	0	3	0.0%

Files with Coverage Reduction	New Missed Lines	%
internal/gen/keys/keys.go	5	12.9%

Totals
Change from base Build 18558293142:	-0.08%
Covered Lines:	6381
Relevant Lines:	11703

---

💛 - Coveralls

[sweatybridge]

The publishable and secrets are drop in replacement for deprecated anon and served role keys. I don't think there's a reason to use old keys?

Can we set utils.CmdSuggestion instead? This way a suggestion to use the new keys is printed on status command, ie.

utils.CmdSuggestion = "Please use publishable key instead of anon key."' 

[stylessh]

how about this?