fix(build): remove NodeJS/Browser specific builds

[wolfy1339]

Resolves #ISSUE_NUMBER

---

Before the change?

• Published a NodeJS build, a Browser build and a neutral source transpilation
• Users who have the moduleResolution option in their tsconfig.json set to bundler couldn't consume the package

After the change?

• Only publishes the neutral source transpilation, as in this case all the builds were the same
• Reduces size of the NPM package
• Users who have the moduleResolution option in their tsconfig.json set to bundler can consume the package

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes
• No

---

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[github-actions]

🎉 This PR is included in version 6.0.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[benjamin-guibert]

@wolfy1339 It likely seems to have solved my "module not found" issue. Thank you for your work! 👌🏻