fix(input_secret): For string secret revert to old form until SDK is updated

[mfori]

No description provided.

[Copilot]

Pull Request Overview

This PR reverts string secret encryption to the legacy format until the SDK supports the new format.

• Add a branch for string values to use the old encrypted string form (prefix:password:value)
• Include a TODO to remove this fallback once the SDK is updated

Comments suppressed due to low confidence (3)

packages/input_secrets/src/input_secrets.ts:51

• There's a new branch handling string values; consider adding or updating unit tests to cover this legacy encryption path.

    if (typeof value === 'string') {

packages/input_secrets/src/input_secrets.ts:49

• [nitpick] The TODO comment would be clearer if it referenced a specific SDK version or tracking issue to know when it can be removed.

    // TODO to make string encryption compatible with current SDK, we need to use the old form.

packages/input_secrets/src/input_secrets.ts:52

• [nitpick] Destructuring here is fine, but consider validating that encryptedPassword and encryptedValue are non-empty strings before formatting the return value.

        const { encryptedValue, encryptedPassword } = publicEncrypt({ value, publicKey });