Rebrand and setup sematic release

[csaba215]

Hi @cconard96.

I created a release workflow for this package and rebranded it as bumbleicons.

Could you please review the changes?

The workflow create the release files, changelog etc. and commits it.

Initial npm setup instructions:

1. Create or use the npm organization cjdevstudios.
2. Make sure your npm user is a member of that org with publish/admin access.
3. Publish the package once manually from this repo:
   npm login
npm publish --access public --provenance
   This creates:
   @cjdevstudios/bumbleicons
4. On npmjs.com, open:
   @cjdevstudios/bumbleicons -> Settings -> Publishing access
5. Add Trusted Publisher:
   Publisher type: GitHub Actions
   Organization/user: CJDevStudios
   Repository: bumbleicons
   Workflow filename: release.yml
   Environment: empty
   After that, publish future releases from GitHub:
   Actions -> Release -> Run workflow

After that, publish future releases from GitHub:
Actions -> Release -> Run workflow

No NPM_TOKEN secret is needed when Trusted Publishing is configured correctly.

If you need more help to make it work just ask and I'll try to help.

[cconard96]

Hello and thank you for your contribution. Just FYI, all of my work on the new Bumble* repositories so far has been done on the "develop" branches. This package should already be rebranded there so I recommend rebasing on that branch and then changing the base for this pull request.

Also, I chose to remove some of the legacy font formats like EOT but if there are legitimate reasons to keep them, I'd be open to restoring them.

[csaba215]

Thank you, I missed the develop branch.

I'll rebase my changes onto develop, sometime tomorrow. (I'll drop the unnecessary changes.)