Refactor the way we add CLI for Microsoft 365 to SPFx Toolkit. Closes #526

[Adam-it]

🎯 Aim

The aim is to refactor SPFx Toolkit to use our own version of CLI for Microsoft 365 npm package instead of the hacky current approach. As a result, I published our own version of CLI for Microsoft 365 for SPFx Toolkit (https://www.npmjs.com/package/@pnp/cli-microsoft365-spfx-toolkit) in CommonJS, and now SPFx Toolkit simply uses this package instead of doing it manually. This simplified development also allows us to have a more formal version of CLI for Microsoft 365 that is based on the official package but has some tweaks created for this project

🧪 Ideas to test

I would suggest to run npm install and vsce package to create the local version of the extension locally and install it in VS Code and click around the SPFx Toolkit mainly focusing on features that use CLI for Microsoft 365 commands.

✅ What was done

• Updated npm package.json to use CLI for Microsoft 365 SPFx Toolkit package and updated all imports
• deleted the hacky script to ingest CLI for Microsoft 365 from the local repo build
• cleaned up contributing guidance
• cleaned up GitHub Workflows not to build CLI for Microsoft 365 repo and added the files manually

🔗 Related issue

Closes: #526

[Adam-it]

ok one point I missed is that we should get rid of fsevents before we proceed

[Adam-it]

Setting this to draft until I solve the fsevents issue

[Adam-it]

Ready for review 🤩

[nicodecleyre]

Thank you for your PR 👏👏👏 ! We'll review is ASAP