Catch NODATA response when generating cache

[AndrewTwydell]

What It Does
Resolves #200

Adds a check for a NODATA response when generating a cache token for the combined trees. If the query comes back with NODATA, an error is thrown by the SDK. This was not handled and ignored by the VSCE.

Review Checklist
I certify that I have:

• tested my changes
• added/updated automated tests
• updated the changelog
• followed the contribution guidelines

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 40.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 28.47%. Comparing base (22639c6) to head (76e8e3c).
Report is 6 commits behind head on main.

Files with missing lines	Patch %	Lines
packages/vsce/src/utils/profileManagement.ts	40.00%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #201      +/-   ##
==========================================
+ Coverage   28.46%   28.47%   +0.01%     
==========================================
  Files         148      148              
  Lines        4954     4958       +4     
  Branches      859      797      -62     
==========================================
+ Hits         1410     1412       +2     
- Misses       3544     3546       +2     

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

[davenice]

I got distracted while looking at this.

It looks good to me. Simpler than our late night marathon last week because most of the logic is similar, we just need to catch the error! And we've already got code to return a blank.

[zFernand0]

LGTM! 😋

[github-actions]

Release succeeded for the main branch. 🎉

The following packages have been published:

• vsce: [email protected]
• vsce: [email protected] (OVSX)

_{Powered by Octorelease 🚀}