GHA: Allow dual release of wolfssl and wolfssl-sys

[kp-shawn-thiah]

Update the release process to allow releasing both together, instead of doing it in separate PRs.

[github-actions]

Code coverage summary for b1e9647:

Filename                             Regions    Missed Regions     Cover   Functions  Missed Functions  Executed       Lines      Missed Lines     Cover    Branches   Missed Branches     Cover
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
wolfssl-sys/src/lib.rs                    34                 0   100.00%           4                 0   100.00%          22                 0   100.00%           0                 0         -
wolfssl/src/aes256.rs                    166                 8    95.18%          11                 0   100.00%         124                 4    96.77%           0                 0         -
wolfssl/src/chacha20_poly1305.rs          75                 2    97.33%           5                 0   100.00%          66                 2    96.97%           0                 0         -
wolfssl/src/context.rs                   401               173    56.86%          41                14    65.85%         286               110    61.54%           0                 0         -
wolfssl/src/error.rs                      44                12    72.73%           5                 1    80.00%          43                10    76.74%           0                 0         -
wolfssl/src/lib.rs                        81                15    81.48%          11                 1    90.91%          72                13    81.94%           0                 0         -
wolfssl/src/rng.rs                        71                 9    87.32%           6                 0   100.00%          42                 3    92.86%           0                 0         -
wolfssl/src/ssl.rs                      1242               334    73.11%          84                25    70.24%         833               246    70.47%           0                 0         -
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
TOTAL                                   2114               553    73.84%         167                41    75.45%        1488               388    73.92%           0                 0         -

✅ Region coverage 73% passes
✅ Line coverage 73% passes

[github-actions]

🚀 Release Plan

🏷️ Release skipped — ignore-release label is applied.

[kp-mariappan-ramasamy]

@kp-shawn-thiah This PR does not update the cargo versions and it is happening in another PR: #342 (comment)

I don't understand, why is the comment in this PR showing we need to release new versions ?

[kp-shawn-thiah]

@kp-shawn-thiah This PR does not update the cargo versions and it is happening in another PR: #342 (comment)

I don't understand, why is the comment in this PR showing we need to release new versions ?

This release plan was generated previously when I was testing the version bumps for the crates. I will add a new job to update the stale release plan when a ignore-release label is added.

[xv-thomas-leong]

Logic looks sane. Some comments on implementation

[xv-thomas-leong]

It seems the new variables you’ve introduced use camelCase, while the existing ones are in snake_case. I have no preference for either style, as JavaScript can be a bit inconsistent in that regard. But could we make sure we stick to one convention within this file for consistency? It was consistent beforehand.

Ideally, we’d enforce this with a linter. However, since this is the only JS file in the project, setting that up is overkill. That said, I’d still like us to keep the naming consistent throughout the file.

[kp-shawn-thiah]

Let me update it to use snake_case to maintain consistency