Refactor: Improve Numeric Validation Logic

[jieyangxchen]

What is the purpose of the change

The purpose of this change is to improve the numeric validation logic in the timeout configuration code. This is achieved by replacing the previous isNotEmpty check with isNumeric and trim, ensuring that only valid numeric values are parsed, which enhances the robustness and readability of the code while reducing the risk of NumberFormatException.

Brief changelog

• Replaced isNotEmpty check with isNumeric and trim to validate numeric input more accurately.
• Optimized the try-catch logic to improve code readability and error handling efficiency.
• Enhanced input validation for timeout configuration to ensure only valid numeric values are parsed.

Verifying this change

This change can be verified by running the existing unit tests that cover timeout configuration scenarios.

Checklist

• Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Add some description to dubbo-website project if you are requesting to add a feature.
• GitHub Actions works fine on your own branch.
• If this contribution is large, please follow the Software Donation Guide.