feat(config): migrate config.toml profiles to the keychain and state.toml

[LorrisSaintGenez]

What

Second step of GROUT-363, stacked on #245: Config.Migrate() gets its body.

• Per config.toml profile: api_key (+ crawler_api_key if set) is stored in the OS keychain under the profile's application ID
• One state.toml entry per application with alias = <profile name>; api_key_uuid left empty (unknown for legacy keys, API lookup comes later)
• current_application_id = the default = true profile's application
• Keychain first, state.toml last (atomic temp + rename via State.Save): a keychain failure aborts before state.toml exists, so the migration retries on the next run
• An empty config.toml still writes an empty state.toml, so the trigger turns off instead of re-firing on every command

config.toml itself is never modified.

Test

# on a machine with legacy config.toml profiles
rm -f ~/.config/algolia/state.toml
go run ./cmd/algolia indices list      # any command triggers the migration
cat ~/.config/algolia/state.toml       # aliases + current_application_id
# macOS: the migrated key is in the keychain (replace <APP_ID>; go-keyring stores it base64-encoded)
security find-generic-password -s algolia-cli -a "app:<APP_ID>" -w | sed "s/^go-keyring-base64://" | base64 -d

GROUT-363

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 23 complexity · 3 duplication

Metric	Results
Complexity	23
Duplication	3

View in Codacy

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