[msal-node-extensions]: Add electron webpack sample

[samuelkubai]

This pull request aims to fix the webpack compatibility issue by doing the following:-

• Fork the node-bindings library with the following changes
• Implement the API changes in node-extensions
• Add the electron webpack sample for msal-node-extensions

Note:
The created fork can be found here

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.24%. Comparing base (1324cee) to head (1c1852c).
⚠️ Report is 3892 commits behind head on dev.

Additional details and impacted files

Flag	Coverage Δ
msal-angular	96.31% <ø> (ø)
msal-browser	88.48% <ø> (∅)
msal-common	85.10% <ø> (ø)
msal-core	76.90% <ø> (ø)
msal-node	81.45% <ø> (ø)
msal-react	94.17% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jasonnutter]

Can you share the changes made in your fork of bindings?

[samuelkubai]

Can you share the changes made in your fork of bindings?

Sure thing, I want to move the changes to a fork under AzureAD, so I can update the pull request.

[jasonnutter]

Looks good! We should setup some time to talk about how we want to approach your fork of bindings long-term, but this is good for now.

[derisen]

LGTM! Apologies for delay, getting node-gyp to work is painful.. Left a minor comment.

[sameerag]

Did we follow up on creating an azure repo for this?

[samuelkubai]

Yes we did, we realized it would take a lot longer to process and thus decided to go on with this setup for the time being as we research on how best to switch to a repo under AzureAD

[sameerag]

Approved. I have a concern merging this - please ensure that your fork is covered under open source licensing so we can proceed with the merge.