refactor: remove dead fork-era code and make VAAS naming consistent

[giunatale]

Pre-release cleanup in three logical commits: dead code out, names made
consistent. No behavior changes.

1. Remove the standalone-changeover path, keep the wire format reserved

The standalone-to-consumer changeover ("preVAAS") was never completed here and
its remnants were dead: the collections, the InitGenesis branch, the keeper
methods, and the standalone staking-keeper plumbing are removed. The two proto
fields stay reserved with comments documenting their intended future use,
so a later implementation can return without a wire-format conflict, and the
transition document is reframed as a forward-looking spec.

2. Remove fork-era dead code and stale comments

The dead IBC v1 port/channel cluster, unused channel-era sentinel errors and
key prefixes, an unused proto message, dead test utilities, hardcoded reserved
chain ids from the upstream project, stale upstream issue references, and the
accumulated stale comments describing code that no longer exists. Also adds a
tidy make target for the multi-module workspace.

3. Naming consistency

• Provider module store name provider -> vaasprovider, matching
  vaasconsumer (pre-release: no migration concerns).
• The CrossChainValidator family -> VaasValidator
  (ApplyCCValidatorChanges -> ApplyVaasValidatorChanges, accessors, proto
  message + regeneration) — the old name described the upstream project's
  architecture, not this one.
• Rewriting the shared event/attribute constant block means a merge with any PR
  that adds a constant there takes this branch's version wholesale and drops
  theirs, so the sibling PRs' additions are defined here too, prefixed where the convention applies (AttributeKeyAckError, EventTypeConsumerEvidenceRejected, EventTypeRetireConsumer, AttributeConsumerClientID); each is harmless ahead of its user.
• Three app/ files carried trailing whitespace inside comments, unformatted on
  main and invisible to make lint (golangci-lint's gofumpt does not flag it,
  gofmt -l does). Normalized.
• Event types unified under a vaas_ prefix.
• The operator guides' command examples swept to the renamed CLI route
  (query provider ... -> query vaasprovider ..., same for tx).
• Package docs for the no_valupdates_* modules, and removal of inert
  plumbing that validated and passed a permanently-false flag.

Also in this PR

• A real lint-configuration bug: the gci import-group list ended with a prefix
  (github.com/atomone-hub/atomone) that matches nothing in this repo, so the
  project's own imports fell into the catch-all group and their placement was
  never enforced. Corrected to github.com/allinbits/vaas, which is what
  AGENTS.md documents, and the resulting import re-sort is applied tree-wide.
  Four inert fork-era exclusion rules are dropped at the same time (two for an
  x/gov directory that does not exist, two targeting a linter that is not
  enabled, one for a migrations path that does not exist).
• All 37 provider *KeyName constants are gone: 24 were unreferenced and the
  other 13 became inline names, matching the 25 collections that already used
  that form — the split was what let the dead two-thirds accumulate unnoticed.
• Two entire files that only declared unused symbols, the fork-era
  IBCTransferKeeper expected keeper (with regenerated mocks), three app
  accessors that no interface requires, several dead e2e helpers, and the last
  CCV-era vocabulary — including three runtime strings an operator could
  actually see.
• Stale comments describing code that no longer exists: a "CCV channel
  handshake" that IBC v2 has no concept of, a test name that was deleted long
  ago, three fictitious interfaces, and prefix names that had been renamed.

Testing

Build, lint, and the full unit suite green; the final tree was verified
byte-identical across the consolidation, and a trial-merge across all open
branches confirmed the rename reconciliation against their new code is a
handful of identifier fixups.

[giunatale]

Branched from giunatale/feat/offline-detection (#63).
Opened against that branch so only this PR's commit shows; will retarget to main after #63 lands and this rebases.

Merge this one last from the series #63 to #75: it renames identifiers that other PRs' new code uses,
so landing it last concentrates the (small) rename reconciliation into its own final rebase instead of rippling through every open PR.

[julienrbrt]

great cleanup

[giunatale]

Note for the final rebase (this PR merges last): two reconciliations cannot land earlier because their sites are not on this branch.

1. The client-authentication chain's MsgSetProviderClient handler emits EventTypeChannelEstablished, a constant this branch deletes; rename that one emission to EventTypeClientEstablished at the rebase (same reconciliation already applied to relay.go here).
2. Re-run the docs CLI-route sweep over doc lines merged after this branch's sweep commit, e.g. fix consumer CLI queries, localnet tooling, and consumer export #74's consumer-liveness command line.

The sibling branches' new event/attribute constants are already pre-defined here (d0d458f) so the constant-block conflicts resolve mechanically.

[giunatale]

The retire event constant pre-defined earlier is dropped again: #78 folded MsgRetireConsumer into MsgRemoveConsumer per review there, so vaas_retire_consumer no longer has a user on any branch. The other pre-defined constants stand.

[giunatale]

Another dead constant to drop at the final rebase, same class as the retire one: #69's review removed the only user of AttributeKeyAckError (the evidence-rejection event no longer carries the ack bytes, since an IBC v2 error ack is a sentinel constant with no application error). Once #69 lands, AttributeKeyAckError has no user on any branch and its declaration in the shared events block should go.