Add symbols support for secret gen function

[BulldromeQ]

This is a pull request template. Please provide the following information to
help us review your pull request.

Please remove placeholder text (including this text)and replace it with your
own content.

Title of the Pull Request

Description

Please provide a summary of your changes here. Include the purpose of the change
and any relevant issues this PR addresses.

Changes

List the major changes you have made in bullet points:

• Change 1
• Change 2
• Change 3

Test Policy Compliance

• I have added or updated unit tests for my changes.
• I have included integration tests where applicable.
• All new and existing tests pass successfully.

Code Quality

• I have followed the coding standards for this project.
• I have performed a self-review of my code.
• My code is well-commented, particularly in areas that may be difficult
  to understand.

Documentation

• I have made corresponding changes to the documentation (if applicable).
• I have updated any relevant READMEs or wiki pages.

Additional Comments

Include any additional comments or context about the PR here.

Checklist

Before you submit this PR, please make sure:

• You have read the contributing guidelines and
  especially the test policy.
• You have thoroughly tested your changes.
• You have followed all the contributing guidelines for this project.
• You understand and agree that your contributions will be publicly available
  under the project's license.

By submitting this pull request, you confirm that my contribution is made under
the terms of the project's license and that you have the authority to grant
these rights.

---

Thank you for your contribution to VMware Secrets Manager
🐢⚡️!

[v0lkan]

\d is regex for "decimal"

\s is regex for "whitespace"; so it might be confusing for the end user.

instead of [\s] it would be better to let users be explicit and use something like [?!;,:.].
(as long as symbols have this; we can use it.

Plus, this solves @yinda’s "no double quotes" comment as if the user does not ask for the double quote, we won’t do the replacement.
That is, we can still have it as an "available symbol" in the constant; but it will be up to the operator to define it.

[BulldromeQ]

Agree, something like [?!;,:.] works fine with limit special characters, I changed \s to \symbol to avoid confusing.

[vmwclabot]

@BulldromeQ, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ab6a5ce must be signed by [email protected]

[vmwclabot]

@BulldromeQ, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ab6a5ce must be signed by [email protected]
• Commit 404b140 must be signed by [email protected]

[vmwclabot]

@BulldromeQ, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ab6a5ce must be signed by [email protected]
• Commit 404b140 must be signed by [email protected]
• Commit d79122a must be signed by [email protected]

[vmwclabot]

@BulldromeQ, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ab6a5ce must be signed by [email protected]
• Commit 404b140 must be signed by [email protected]
• Commit d79122a must be signed by [email protected]
• Commit 794e7a5 must be signed by [email protected]

[vmwclabot]

@BulldromeQ, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ab6a5ce must be signed by [email protected]
• Commit 404b140 must be signed by [email protected]
• Commit d79122a must be signed by [email protected]
• Commit 794e7a5 must be signed by [email protected]

[vmwclabot]

@BulldromeQ, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ab6a5ce must be signed by [email protected]
• Commit 404b140 must be signed by [email protected]
• Commit d79122a must be signed by [email protected]
• Commit 794e7a5 must be signed by [email protected]

[vmwclabot]

@BulldromeQ, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ab6a5ce must be signed by [email protected]
• Commit 404b140 must be signed by [email protected]
• Commit d79122a must be signed by [email protected]
• Commit 794e7a5 must be signed by [email protected]

[vmwclabot]

@BulldromeQ, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ab6a5ce must be signed by [email protected]
• Commit 404b140 must be signed by [email protected]
• Commit d79122a must be signed by [email protected]
• Commit 794e7a5 must be signed by [email protected]

[vmwclabot]

@BulldromeQ, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ab6a5ce must be signed by [email protected]
• Commit 404b140 must be signed by [email protected]
• Commit d79122a must be signed by [email protected]
• Commit 794e7a5 must be signed by [email protected]

[v0lkan]

@BulldromeQ, I updated the escape sequence to \x instead of \symbol as it might get mixed up in (unlikely) cases of \s (a whitespace) followed by a literal “ymbol”.

\x is a less-used flag which modern engines prefer to use ^ and $ instead of \x, so we should be safe in there.

I ran the tests and it passes.

I’m merging this one.