chore: add v0.50.2 changelog to main

[julienrbrt]

Description

Closes: #XXXX

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

• New Features

  • Public keys can now be used and saved in base64 encoding.
  • Telemetry now supports statsd and dogstatsd.
  • New shutdown-grace flag for controlled server shutdown.
  • Ability to display additional version information with --long flag.

• Enhancements

  • Improved querying for government proposals.
  • Added a flag to disable colored logs in the server module.

• Bug Fixes

  • Resolved an issue with FinalizeBlock calls in the baseapp module.
  • Ensured post handlers run for all transaction executions, regardless of success.
  • Fixed a compatibility issue with gogoproto.Merge.

• Documentation

  • Updated changelogs with new release versions and links to GitHub releases.

• Refactor

  • Removed outdated dependencies in favor of official protobuf types.

• Chores

  • Released new version v0.1.1 with updated go-getter settings.

[coderabbitai]

Walkthrough

Walkthrough

The recent updates introduce enhancements and fixes across various modules. Public keys can now be saved in base64 format, server shutdowns can be gracefully delayed, and telemetry supports new sinks. Additionally, the logging can be color-disabled, and the governance querying and version display have been improved. The baseapp module sees several fixes, including proper handling of consensus parameters, transaction simulation, block finalization, and post-handler execution. A problematic merge function has also been corrected. New versions have been released for tools and upgrade modules.

Changes

File Path	Summary of Changes
client/keys, server, telemetry, x/gov, version, baseapp	Enhanced public key handling, server shutdown, telemetry sinks, governance querying, version info, and baseapp functionality.
tools/confix/..., x/upgrade/...	Introduced new release versions with associated improvements.

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 X ?

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

Note: For conversation with the bot, please use the review comments on code diffs or files.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 978fffc and 773fdf7.

Files selected for processing (4)

• CHANGELOG.md (2 hunks)
• tools/confix/CHANGELOG.md (1 hunks)
• x/auth/CHANGELOG.md (1 hunks)
• x/upgrade/CHANGELOG.md (1 hunks)

Files skipped from review due to trivial changes (2)

• tools/confix/CHANGELOG.md
• x/auth/CHANGELOG.md

Additional comments: 3

CHANGELOG.md (1)

• 45-80: > Note: This review was outside the patches, so it was mapped to the patch with the greatest overlap. Original lines [1-1255]

Please verify the following key points in the provided changelog:

• Ensure that all breaking changes are clearly documented and justified.
• Confirm that security vulnerabilities have been addressed and that the fixes do not introduce new issues.
• Check that new features have been properly tested and do not conflict with existing functionality.
• Validate that bug fixes resolve the issues without causing regressions.
• Review improvements for potential impacts on performance and stability.

x/upgrade/CHANGELOG.md (2)

• 28-32: The changelog update correctly adds a new version entry v0.1.1 with a corresponding improvement. The link to the GitHub release and the pull request reference are properly formatted and follow the established changelog conventions.

• 28-28: Verify the version number v0.1.1 in the changelog entry against the PR title "chore: add v0.50.2 changelog to main". There seems to be a discrepancy in the version numbers.