Use dynamic version from plugins.json for manual workflow

[mukeshpanchal27]

Summary

This PR mainly improves the manual workflow for standalone plugin releases.

• Replaced the text input for the slug with a dropdown to select the specific modules so we don't get any human error if someone mistypes the slug.
• Remove version input
• How does the version work for automated and manual workflows?
  • Automated workflow: It will read the plugins.json file and based on json config it setup the standalone plugin.
  • Manual workflow: Based on the input slug the script will find the version for it, If the selected plugin slug is not present in plugins.json then trigger a failure and exit the workflow.

Also use test SVN credential so we can't release the plugin when doing testing.

I already open PR 10up/action-wordpress-plugin-deploy#122 that support the debug mode in deploy process. Once it will approve we can use DRY_RUN ENV variable for testing.

Fixes #703

Checklist

• PR has either [Focus] or Infrastructure label.
• PR has a [Type] label.
• PR has a milestone or the no milestone label.

[felixarntz]

@mukeshpanchal27 Logic-wise this looks great. I have two comments for things to improve though, particularly the hard-coded options are not desirable as they are duplicated from what should be in plugins.json instead.

[felixarntz]

@mukeshpanchal27 Thanks, this looks great now!

One additional comment for consideration, though not necessarily a blocker.

[joemcgill]

This is working for me. 👍🏻

[felixarntz]

@mukeshpanchal27 Note that the DRY_RUN PR has now been merged upstream. So it would be great to incorporate that here.

Dismissing my review until the debugging code is updated

[mukeshpanchal27]

@mukeshpanchal27 Note that the DRY_RUN PR has now been merged upstream. So it would be great to incorporate that here.

@felixarntz The DRY_RUN PR has been merged into develop branch, not the stable branch, so we can't use it. If we have to use DRY_RUN then we have to use the develop branch, or we will use it once it is merged into the stable branch. cc. @joemcgill

[felixarntz]

Thanks @mukeshpanchal27, in that case let's do that separately. Could you please open a tracking issue for us to set up DRY_RUN in the future once it becomes available in a stable version of the action?

[felixarntz]

@mukeshpanchal27 Thanks, LGTM!

Just a reminder to update the below prior to merging.

[mukeshpanchal27]

Thanks @mukeshpanchal27, in that case let's do that separately. Could you please open a tracking issue for us to set up DRY_RUN in the future once it becomes available in a stable version of the action?

@felixarntz, should we consider opening a separate issue to set up the DRY_RUN option? By doing so, the changes made will not be uploaded to SVN. This approach could be useful for testing the process before committing any actual changes. What are your thoughts on this?

[felixarntz]

@mukeshpanchal27 Yes that's what I meant. We could somehow configure it I think so that for example in pull requests it is always set to have DRY_RUN enabled.

[joemcgill]

The latest updates look right to me. Thanks @mukeshpanchal27!