Move buggy bootstrap-icons dependency to core/package.json

[kaixin-hc]

What is the purpose of this pull request?

• Documentation update
• Bug fix
• Feature addition or enhancement
• Code maintenance
• DevOps
• Improve developer experience
• Others, please explain:

Addresses #2538

Overview of changes:
Moving of the dependency. The file packages/core/package.json is also where the other icon dependencies live.

Anything you'd like to highlight/discuss:
See comments on issue. Also, testing may be misleading CI passing, local passing even with the erroneous code, and some websites deploying fine on 5.5.0 (eg markbind website).

Also, I have no idea why that last bracket is marked as a change. It looks the same to me???

Testing instructions:
Ideas on how else to test appreciated.

Reproducing issue notes:

1. You can verify this issue exists locally by making sure you are using the npm installed version and that you have no other markbind on your device + markbind is not npm linked to your local development repository
2. When I linked to markbind 5.5.0 locally, this crashes... until I ran npm setup, which made all sites work

Testing this PR:

1. Locally, npm run setup after these changes results in the local sites working 😓 😅

Proposed commit message: (wrap lines at 72 characters)
Move buggy bootstrap-icons dependency to core/package.json

---

Checklist: ☑️

• Updated the documentation for feature additions and enhancements
• Added tests for bug fixes or features
• Linked all related issues
• No unrelated changes

---

Reviewer checklist:

Indicate the SEMVER impact of the PR:

• Major (when you make incompatible API changes)
• Minor (when you add functionality in a backward compatible manner)
• Patch (when you make backward compatible bug fixes)

At the end of the review, please label the PR with the appropriate label: r.Major, r.Minor, r.Patch.

Breaking change release note preparation (if applicable):

• To be included in the release note for any feature that is made obsolete/breaking

Give a brief explanation note about:

• what was the old feature that was made obsolete
• any replacement feature (if any), and
• how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

[damithc]

Thanks for the quick fix @kaixin-hc

[EltonGohJH]

I think this should fix the problem even if it dun it is still a good idea to shift it anyway.

So, we can merge it in!

[yiwen101]

LGTM
Thank you for the quick investigation and fix