ADR-18 outdated upgrade information

[rootulp]

Context

celestia-app/docs/architecture/adr-018-network-upgrades.md

Line 47 in 1819f96

The height of the upgrades will initially be hard coded into the binary. This will consist of a mapping from chain ID to app version to a range of heights that will be loaded by the application into working memory whenever the node begins and supplied directly to the `upgrades` module which will be responsible for scheduling. The chainID is required as we expect the same binary to be used across testnets and mainnet. There are a few considerations that shape how this system will work:

Problem

We won't have a hard-coded version height. Node operators will provide the v2 upgrade height via --v2-upgrade-height. We're also not using the Cosmos SDK x/upgrade module