Refactor: Updated signMessage to use util::Expected and removed SigningResult::OK #35201

Summary

Similar to #32958 and #35105.

We now are using util::Expected and removed SigningResult::OK

This makes the enum less confusing because now it no longer includes OK and is now a pure error enum.

<!--e57a25ab6845829454e8d69fc972939a-->

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

<!--006a51241073e994b41acfe9ec718e94-->

Code Coverage & Benchmarks

For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/35201.

<!--021abf342d371248e50ceaed478a90ca-->

Reviews

See the guideline for information on the review process. A summary of reviews will appear here.

<!--174a7506f384e20aa4161008e828411d-->

Conflicts

Reviewers, this pull request conflicts with the following ones:

• #35444 (wallet: make descriptor SPKM mutex non-recursive by w0xlt)
• #35436 (wallet: Add addHDkey interface by pseudoramdom)
• #34617 (fees: wallet: remove block policy fee estimator internals from wallet by ismaelsadeeq)
• #34520 (refactor: Add [[nodiscard]] to functions returning bool+mutable ref by maflcko)
• #34075 (fees: Introduce Mempool Based Fee Estimation to reduce overestimation by ismaelsadeeq)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

<!--5faf32d7da4f0f540f40219e4f7537a3-->

<!--85328a0da195eb286784d51f73fa0af9-->

🚧 At least one of the CI tasks failed. _{Task test ancestor commits: https://github.com/bitcoin/bitcoin/actions/runs/25280307633/job/74116469483} _{LLM reason (✨ experimental): CI failed due to a Clang -Werror build error: the switch in signverifymessagedialog.cpp doesn’t handle the OK enum value.}

<details><summary>Hints</summary>

Try to run the tests locally, according to the documentation. However, a CI failure may still happen due to a number of reasons, for example:

• Possibly due to a silent merge conflict (the changes in this pull request being incompatible with the current code in the target branch). If so, make sure to rebase on the latest commit of the target branch.

• A sanitizer issue, which can only be found by compiling with the sanitizer and running the affected test.

• An intermittent issue.

Leave a comment here, if you need help tracking down a confusing failure.

</details>

Looks like the CI failure is fixed with this PR #35202 will rebase onto master once it's merged to get the CI passing

rebased to e14b3ff

The CI should pass now

rebased and resolved conflicts in 5cc8436