Prune upgrade handlers

[Taztingo]

Description

Removes unused navs and upgrade handlers to improve build time.

closes: #1920

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer
• Review Codecov Report in the comment section below once CI passes

Summary by CodeRabbit

• Chores

  • Removed unused navigation elements to enhance the interface.
  • Updated backend services for improved performance.
  • Upgraded to a newer version of the software development kit for enhanced features and security.

• Refactor

  • Restructured upgrade handling for better system maintenance.
  • Deprecated and removed outdated upgrade functions and tests for a cleaner codebase.

[coderabbitai]

Walkthrough

The recent changes streamline the codebase by removing unused elements, specifically related to upgrade handlers and tests for specific upgrade versions. The updates also include dependency version bump and restructuring of functions to improve build efficiency and reduce complexities causing long build times.

Changes

File(s)	Change Summary
CHANGELOG.md	Removed unused navigation elements, updated app.go, and bumped SDK version.
app/upgrades.go	Restructured upgrade handlers, removed specific upgrade functions.
app/upgrades_test.go	Removed test functions for specific upgrade scenarios.

Assessment against linked issues

Objective	Addressed	Explanation
Prune upgrade handlers for 1.19 (#1920)	✅
Reduce build times by deleting unused navs (#1920)	✅
Streamline app.go and upgrades.go (#1920)	✅

Poem

In the code's lush garden, we prune with care,
Efficiency blooms with changes rare. 🌿
Handlers gone, tests take flight,
Lighter codebase, future bright.
With a leap and a bound, the rabbit sings,
"Onward to progress, with streamlined wings!" 🚀
🐰💻🌟

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 44648d5 and 28e17d2.

Files selected for processing (1)

• CHANGELOG.md (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• CHANGELOG.md

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1