fix: Only apply v8 fork logic on osmosis-1

[joeabbey]

Closes: #1609

What is the purpose of the change

The v8 fork contained parameter changes that were only applicable on the "osmosis-1" chainID.

Brief Changelog

Limiting the RunForkLogic to osmosis-1

Testing and Verifying

This change is a trivial rework / code cleanup without any test coverage.

[codecov-commenter]

Codecov Report

Merging #1610 (a6e34a2) into main (2d8b9bd) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1610      +/-   ##
==========================================
- Coverage   19.60%   19.60%   -0.01%     
==========================================
  Files         242      242              
  Lines       32277    32279       +2     
==========================================
  Hits         6329     6329              
- Misses      24790    24792       +2     
  Partials     1158     1158              

Impacted Files	Coverage Δ
app/upgrades/v8/forks.go	0.00% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2d8b9bd...a6e34a2. Read the comment docs.

[andrewl33]

Would a test that runs through all upgrades catch regressions like this going forward?

The tests could be fast if upgrade heights were in sequential.
It would mean these values would have to be overridable though, which might've been done before.

[ValarDragon]

I think what should be done going forward is we add a flag / genesis file value for whether a given fork is following the Osmosis mainnet-only upgrades (things that refer to specific pool ID's, or incentive adjustments, etc.)