feat: migrate to v1.0.0 for package manager compliance (atomic Go module migration)

[vxfemboy]

⚠️ Why This PR Exceeds the 5-File Limit

I understand the preference for PRs with ≤5 files modified. However, this Go module path migration must be atomic to prevent CI failures and build breakage.

Technical Constraint: Go Module Migration Must Be Atomic

When changing a Go module path in go.mod, all import statements across the entire codebase must be updated simultaneously in the same commit/PR. Here's why:

// In go.mod
module github.com/vmfunc/sif  // ← If we change this...

// Then ALL of these break immediately:
import "github.com/dropalldatabases/sif/internal/config"  // ❌ Won't compile
import "github.com/dropalldatabases/sif/internal/scan"    // ❌ Won't compile

If split into multiple PRs:

1. PR Base scanning doesn't occur even when --noscan is present #1 changes go.mod → All subsequent PRs fail CI (can't import old path)
2. PR 🎀 feat: Shodan Integration #2 tries to fix imports → Can't merge until PR Base scanning doesn't occur even when --noscan is present #1 merges (circular dependency)
3. Main branch is broken between merges
4. All CI checks fail until every PR merges

The only working approach: Change go.mod + all imports in a single atomic PR.

What We're Doing About the File Count

To minimize impact, we're splitting independent changes into separate PRs:

• ✅ Can be separate PR: Domain fixes (remove references to lunchcat domain #50) - Makefile, .all-contributorsrc, README.md contributor links
• ✅ Can be separate PR: Discord link standardization - CONTRIBUTING.md, docs/README.md
• ⚠️ MUST be atomic: Module path migration - 36+ files (this PR)

This PR only contains the atomic Go module migration that cannot be split without breaking the build.

[vxfemboy]

[vmfunc]

blocked by #63, #64 and #62

[vxfemboy]

@vmfunc resolved

[vmfunc]

CI fails

https://github.com/vmfunc/sif/actions/runs/20904759232/job/61984190064?pr=59

[vmfunc]

hey, thanks for pushing on this - the module path migration is needed and the approach is right (atomic, single PR). couple things though:

build-breaking issues:

• sif.go removes the internal/scan/builtin import but still calls builtin.Register() on two lines - that won't compile
• the entire internal/scan/builtin/ package (5 files) still has dropalldatabases imports and isn't touched by this PR at all - register.go, shodan_module.go, whois_module.go, frameworks_module.go, nuclei_module.go all need the import swap

missed files:

• .github/workflows/release.yml - has go install github.com/dropalldatabases/sif/cmd/sif@v...
• .golangci.yml - has github.com/dropalldatabases/sif/internal/logger.Write in the errcheck exclude

also needs a rebase - main has diverged significantly (new lint config, dependency bumps, CI changes). that's probably why CI is failing on top of the missing files.

the CHANGELOG is nice but pretty heavy for this project's style - we haven't maintained one before and i'd rather not start now. the release notes on the tag are enough. would prefer to drop that file from this PR.

once the builtin package + those config files are updated and it's rebased, this should be good to go.