Add SDK getCache method

[AndrewTwydell]

Requires #171 - Merged!

What It Does
Resolves #169

Adds getCache method to the SDK to retrieve a cached result from CMCI using a cache token returned by getResource.

This will allow the VSCE to paginate large result sets using the SDK rather than axios HTTP requests.

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

All modified and coverable lines are covered by tests ✅

Project coverage is 93.81%. Comparing base (1ea123b) to head (d3b74e1).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #172      +/-   ##
==========================================
+ Coverage   93.62%   93.81%   +0.18%     
==========================================
  Files          74       75       +1     
  Lines         753      776      +23     
  Branches       41       45       +4     
==========================================
+ Hits          705      728      +23     
  Misses         48       48              

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

[davenice]

Looks good I think.

[zFernand0]

LGTM! 😋
For these new set of APIs, (as well as SUMMONLY, NODISCARD, OVERRIDEWARNINGCOUNT), Could we add some system tests?

Depending on people's environment, having system tests might help determine whether the APIs work as expected, or if there are edge cases to consider 😋

---

We could handle system tests in a follow up PR (for both, cache, and the new query params) if you'd like to get this one merged sooner rather than later 🙏

---

Update: Created the issue below:

• TD: Add system tests for newer APIs and parameters #176

[zFernand0]

The functionality works great!
I like the pagination use case.

I was playing around, but I could not properly test the OVERRIDEWARNINGCOUNT queryParm (likely because the DEFAULTWARNCNT was never specified during the WUI configuration) 😢

I say "Let's keep moving forward" and let's handle the system tests in a separate PR 🙏

---

For those testing...

Feel free to use this script

/* Save this file as `test.mjs` and run `node test.mjs` */

import { ProfileInfo } from "@zowe/imperative";
import * as sdk from "@zowe/cics-for-zowe-sdk";

(async () => {
    const profInfo = new ProfileInfo("zowe");
    await profInfo.readProfilesFromDisk();
    const profAttrs = profInfo.getDefaultProfile("cics");
    const mergedArgs = profInfo.mergeArgsForProfile(profAttrs, { getSecureVals: true });
    const session = ProfileInfo.createSession(mergedArgs.knownArgs);

    let response;
    response = (await sdk.getResource(session, {name: "CICSCSDResource", queryParams: {summonly: true, nodiscard: true}}));
    const cacheToken = response.response.resultsummary.cachetoken;
    console.log("Cache token: ", cacheToken);

    // Use the above cache token and play around with the `startIndex` and `count` values
    response = (await sdk.getCache(session, {cacheToken, startIndex:1, count:100})).response.records.cicscsdresource.map(x => x.defname);
    console.log(response);
})().catch((err) => {
    console.error(err);
    process.exit(1);
});