feat(config): apply skip rules during the config.toml migration

[LorrisSaintGenez]

What

Third step of GROUT-363, stacked on #246: the migration skip rules, applied before any keychain write.

• admin_api_key never moves to the new model: one log line points to ALGOLIA_ADMIN_API_KEY / --api-key instead, whether the profile migrates or not
• A profile without application_id or with an empty api_key has nothing usable to migrate: skipped + log
• Profiles sharing the same application_id would overwrite each other's keychain entry: the default = true profile wins, the others are logged as conflicts and skipped
• Profiles are processed in name order so conflict resolution and logs stay deterministic (ConfiguredProfiles iterates a map)

Test

# config.toml with: a profile with an empty api_key, two profiles sharing
# the same application_id (one default), and an admin_api_key-only profile
rm -f ~/.config/algolia/state.toml
go run ./cmd/algolia indices list      # one log line per skip, once
cat ~/.config/algolia/state.toml       # only the default profile's entry remains

GROUT-363

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 15 complexity · 1 duplication

Metric	Results
Complexity	15
Duplication	1

View in Codacy

_{TIP This summary will be updated as you push new changes.}