Updates CLI API usage docs. Closes #5699

[officialasishkumar]

Closes #5699

Summary

• Corrects the spo web get API example to use the url option.
• Adds concise ESM setup guidance for Node.js apps using the CLI API.

Validation

• npm run build (docs)

[milanholemans]

Hi @officialasishkumar, can you please first claim the issue before working on it?
Thanks

[officialasishkumar]

Commented on #5699 now for tracking.

[Adam-it]

@officialasishkumar In general, the change is in the right direction, but let's refactor it to be a bit clearer before we merge.

[Adam-it]

In general, this is what was described in the related issue, but what I think @martinlingstuyl intention was to simply extend the ## Integrate CLI for Microsoft 365 in your app section below with an additional few sentences that would explain that CLI for Microsoft 365 is an ES module and an app that will use it should be ES Module as well. It should also explain to use npm install @pnp/cli-microsoft365 to add the package. Let's also not imply ..."latest", I think mentioning how to install it will be enough, using latest in package.json for any npm package is generally not a safe approach as you may easily end up with a breaking change on the next npm install, so we should rather not recomment this in our docs

[officialasishkumar]

Updated in 58a6dbb: moved the ES module and install guidance into the existing integration section and removed the package.json/latest example.

[Adam-it]

hi, due to a patch release, we needed to perform we had to rebase the main branch, which now makes this PR out of sync with the latest state of main.
@officialasishkumar may I kindly ask you to rebase this branch against the latest main before we proceed with the review? Thanks

[officialasishkumar]

Done in 56a9a85: rebased the branch onto latest main. The obsolete version-bump commit was already upstream, so the PR diff is now just the CLI API docs update.

[officialasishkumar]

Rebased this branch onto the latest main in 140fcf8.