[ConfigManager] Register Node Sections 3/4

[bdchatham]

What this does

Declares the last five tables in the node's configuration file: state sync, the
transaction index, instrumentation, the signing key paths, and self remediation.
33 keys. Nothing consumes them, so a node's configuration reads exactly as it did.

After this every table in that file is declared. The keys at its top are the
remaining step.

What varies by node kind

One key. A node that serves queries indexes transactions so it can answer them, and
a validator and a seed serve none, so they index nothing and keep the write.

Key	validator	seed	full and archive
tx-index.indexer	[null]	[null]	[kv]

The other four sections answer the same for every mode, and each says why in the
source. Whether a node starts from a snapshot is a decision about how it is brought
up rather than about what it will be. What a node measures about itself follows from
how it is operated. The signing key paths are unused by a node that does not sign,
so varying them would state a difference the binary does not make. The self
remediation thresholds each describe a node that has stopped making progress, which
is the same condition whatever the node is for.

The paths left out

The signing key section carries the root directory field the node fills from the command line
after the file is read, and it is the one where a blank root is worst: a node that cannot find
its key does not sign. That is the last of the five sections carrying that field.

The one path left out for a reason of its own

statesync.rpc-servers names the servers to fetch a snapshot from, and they are the
operator's own peers. There is no value to inherit: an empty list is not a default
anyone can start from, and an address written here would name a host this binary
cannot know exists. A test fails if the node ever ships one, and the key should then
be declared.

Two tests worth naming

One walks the section names this package owns rather than a list kept beside them,
so the next section is covered by registering it and not by remembering to extend a
list.

The other asserts the registry refused nothing. That is the check no single section
can make: two of the refusals depend on what else has registered, a section that
loses one is dropped whole with every key it declared, and a dropped section is
absent rather than loud.

Verification

gofmt, goimports, go vet clean. golangci-lint reports nothing on the touched
package. config/... and cmd/seid/... pass.

Reviewing this

Third of four, stacked on the second, so the diff shows only this step.

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Aug 25, 2026, 1:20 AM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.61%. Comparing base (44f76d2) to head (ecc927b).

Additional details and impacted files

@@                   Coverage Diff                    @@
##           plt-775-node-sections-2    #3994   +/-   ##
========================================================
  Coverage                    57.60%   57.61%           
========================================================
  Files                         2230     2230           
  Lines                       187668   187682   +14     
========================================================
+ Hits                        108112   108126   +14     
  Misses                       69689    69689           
  Partials                      9867     9867           

Flag	Coverage Δ
sei-chain-pr	100.00% <100.00%> (ø)
sei-db	69.80% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
config/tendermintbase/tendermintbase.go	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.