br: have better crypter key error msg

[Tristan1900]

What problem does this PR solve?

Issue Number: close #56388

Problem Summary:

What changed and how does it work?

1. checks the error of decoding hex format on crypto key and return a customized error indicating the hex format is not valid
2. added tests to verify that

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[codecov]

Codecov Report

Attention: Patch coverage is 41.66667% with 21 lines in your changes missing coverage. Please review.

Project coverage is 57.5533%. Comparing base (0f6bddd) to head (e4f537d).
Report is 46 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #56589         +/-   ##
=================================================
- Coverage   73.3958%   57.5533%   -15.8426%     
=================================================
  Files          1628       1754        +126     
  Lines        449554     638950     +189396     
=================================================
+ Hits         329954     367737      +37783     
- Misses        99344     247039     +147695     
- Partials      20256      24174       +3918     

Flag	Coverage Δ
integration	38.6917% <41.6666%> (?)
unit	73.2737% <22.2222%> (+0.7554%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	63.1248% <41.6666%> (+17.5301%)	⬆️

[Tristan1900]

/retest

[tiprow]

@Tristan1900: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger, YuJuncen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• br/OWNERS [BornChanger,YuJuncen]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-10-16 02:00:12.541936913 +0000 UTC m=+409209.690846745: ☑️ agreed by YuJuncen.
• 2024-10-17 12:52:59.028979934 +0000 UTC m=+534776.177889759: ☑️ agreed by BornChanger.

[tiprow]

@Tristan1900: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	e4f537d	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.