fix: added .npmignore file so dist is added in npm release

[abdullahwaheed]

No description provided.

[adamstankiewicz]

Approved, but I would recommend continuing to include now-removed @semantic-release/github step to ensure GitHub releases are created during the release.yml workflow before merging.

[adamstankiewicz]

This is removing @semantic-release/github, but I believe we would still want this condition. Related to verifyConditions, including @semantic-release/github here ensures the "precense and validity of the authentication [with GitHub]".

Subsequently, when @semantic-release/github is used within publish below, it ensures a GitHub release is created in the repository.

Note, the assets.path configuration currently used with @semantic-release/github can likely stay, pointing to dist. It controls which files are included in a release's archive files (e.g., see "Assets" on the GitHub release for the recently published v4).

[adamstankiewicz]

@abdullahwaheed Looks like this PR was reverted because the release workflow failed with the following error:

[9:46:23 AM] [semantic-release] › ✘  ENOPKG Missing `package.json` file.
A package.json file (https://docs.npmjs.com/files/package.json) at the root of your project is required to release on npm.

FWIW, this may likely have resulted due to the removal of the /* from the assets path; I would have left that assets config unchanged. Per the documentation, the assets config accepts Glob patterns, which requires the /* to exist.

For example, using a Glob string tester tool:

Without /* in assets

With /* in assets

Note how the test strings do NOT match without /*. As a result, the @semantic-release/github plugin did not find package.json because the Glob pattern didn't match the files contained within dist without /* included.