chore: Fixed changelog duplicated items

[bizk]

Description

Removes duplicated changelog items on 18026

---

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

[coderabbitai]

Walkthrough

The project has undergone two significant updates. The first update involves the implementation of a streaming JSON parser to efficiently extract the chain-id from the genesis file, enhancing the parsing process. The second update focuses on the cryptographic aspect, where the crypto/keys module has been modified to generate public keys using the secp256k1 curve in constant time, improving security by mitigating timing attacks.

Changes

Files Affected	Summary of Changes
Various files in .../parser/	Implemented a streaming JSON parser for parsing chain-id from the genesis file.
Files in crypto/keys/secp256k1	Modified to ensure constant-time public key generation on secp256k1.

---

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 b6f9c70 and 92b5dde.

Files selected for processing (1)

• CHANGELOG.md (1 hunks)

Additional comments: 2

CHANGELOG.md (2)

• 67-68: The changelog entry for PR feat: secp256k1 public key constant time #18026 is correctly listed, aligning with the summary provided earlier.

• 65-67: The changelog entries appear to be correctly formatted and include the appropriate PR links and descriptions.