fix: 'upgrade' output includes SDK when inside a project dir

[zimeg]

Summary

This PR updates outputs of the upgrade command to note if the latest SDK versions were checked.

Preview

Outputs now change depending on the path used 👾

$ slack version
Using slack v3.0.4
$ slack upgrade
✔ You are using the latest Slack CLI version
$ slack create asdf
$ cd asdf
$ slack upgrade
✔ You are using the latest Slack CLI and SDK versions

Reviewers

A handbuilt make of these changes might be useful for testing the shown version:

$ go build -ldflags="-X 'github.com/slackapi/slack-cli/internal/pkg/version.Version=3.0.4'" -o bin/slack

And these commands can be useful in testing cases with a bolt JS project:

$ npm install @slack/[email protected]
$ npm install @slack/cli-hooks@latest

Requirements

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 7 lines in your changes missing coverage. Please review.

Project coverage is 62.89%. Comparing base (758884c) to head (6bde33d).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
cmd/upgrade/upgrade.go	0.00%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #46      +/-   ##
==========================================
- Coverage   62.93%   62.89%   -0.05%     
==========================================
  Files         210      210              
  Lines       22147    22152       +5     
==========================================
- Hits        13938    13932       -6     
- Misses       7126     7134       +8     
- Partials     1083     1086       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mwbrooks]

✅ Works well and looks good to me! Thanks for tightening up the UX here @zimeg!

Running upgrade OUTSIDE a project directory:

Running upgrade INSIDE a project directory:

[zimeg]

@mwbrooks Thanks so much for sharing these previews 📺 ✨

I'm eager to merge this now but am wanting to check one or two more things with tests before so. One strange thing happening on the latest commit I notice is two runs of E2E test status. AFAICT this is from other experiments unrelated.

Another unrelated test change relates to cleaning up the artifacts used in testing forked changes after a merge!

[zimeg]

@mwbrooks Thanks yet again for a review and preview.

Tests are passing as we might hope for these changes. I will merge this now for the next release with hopes that this next upgrade will be more clear 🫡