Add crypto timeout - step 1

[miyazakh]

Add crypto timeout to RNG and AES

The changes add timeout control logic to cryptographic operations under the wolfHSM framework. The modifications allow the client to enforce a maximum allowed time for crypto operations.

Added new callback function pointers to the relevant configuration/context structures to support timeout handling. These callbacks allow the application to provide custom time-related functions, such as:

• Getting the current time (GetCurrentTime)
• Checking whether the timeout has expired (CheckTimeout)

When the crypt-timeout feature is enabled, the GetCurrentTime callback must be provided as a user-defined function. If the CheckTimeout callback is not defined, internal default implementation is used.

Added a new build-time configuration macro:

• WOLFHSM_CFG_ENABLE_CLIENT_CRYPTIMEOUT

This macro enables the client-side cryptographic timeout feature.When enabled, the wolfHSM client checks for timeout conditions during cryptographic operations.

The feature has been added to RNG and AES. It will be extended to the remaining cryptographic algorithms once this PR is approved.

For testing, make CRYPTIMEOUT=1 enables the items in tests/ folder.

[douzzer]

@miyazakh conflicts to resolve

[miyazakh]

resolve conflicts and issues after rebase. Updated based on Copilot’s suggestions