chore: release v0.1.0

[lidel]

• LICENSE: rewrite as standard plain-text MIT so GitHub and pkg.go.dev detect it (was broken by // comment prefixes and mixed-license format, causing pkg.go.dev to suppress all documentation)
• SPDX headers: replace 19-line MIT preamble in bbloom.go with SPDX-License-Identifier: MIT, add SPDX-License-Identifier: CC0-1.0 to sipHash.go
• godoc: add ExampleNew, ExampleNewWithKeys, ExampleBloom_Has, ExampleJSONUnmarshal; expand docs on NewWithBoolset, NewWithBoolsetAndKeys, Bloom.Mtx
• README: explain fork history, IPFS usage (blockstore bloom cache, DAG walker dedup)
• version: bump to v0.1.0

[github-actions]

Suggested tag: v0.1.0

Comparing to: v0.0.4 (diff)

Changes in configuration file(s):

diff --git a/go.mod b/go.mod
index d215f4f..4e0112c 100644
--- a/go.mod
+++ b/go.mod
@@ -1,3 +1,3 @@
 module github.com/ipfs/bbloom
 
-go 1.12
+go 1.25

gorelease says:

# github.com/ipfs/bbloom
## compatible changes
NewWithBoolsetAndKeys: added
NewWithKeys: added

# summary
Suggested version: v0.1.0

gocompat says:

HEAD is now at 627bb99 Merge pull request #6 from ipfs/fix/odd-ends
Previous HEAD position was 627bb99 Merge pull request #6 from ipfs/fix/odd-ends
Switched to branch 'master'
Your branch is up to date with 'origin/master'.

Cutting a Release (and modifying code files)

This PR is modifying both version.json and code files (not markdown, YAML, TOML or lock files).
The Release Checker is not able to analyse files that are not checked in to master. This might cause the above analysis to be inaccurate.
Please consider performing all the code changes in a separate PR before cutting the release.

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.