AfterEpochEnd called with wrong epoch number

[czarcas7ic]

This PR calls EpochEnd prior to increasing the CurrentEpoch by 1 as discussed here

Once approved, I will advise all integrators to test their systems off main before we push this to the next 7.x release (before we do this, I think we need to base main off 7.0.2, its still on 7.0.0 I believe)

---

For contributor use:

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer

[codecov-commenter]

Codecov Report

Merging #1043 (84da8ea) into main (a5589e0) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1043   +/-   ##
=======================================
  Coverage   20.60%   20.60%           
=======================================
  Files         193      193           
  Lines       25237    25237           
=======================================
  Hits         5199     5199           
  Misses      19084    19084           
  Partials      954      954           

Impacted Files	Coverage Δ
x/epochs/abci.go	100.00% <100.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 a5589e0...84da8ea. Read the comment docs.

[mattverse]

Does simply calling AfterEpochEnd with the incremented epoch number fix the bug?
Just curious, AfterEpochEnd(https://github.com/osmosis-labs/osmosis/blob/main/x/incentives/keeper/hooks.go#L13-L45) doesn't seem like it's doing anything with the epochNumber, or I might simply be missing some part