feat: add support for 'task' deployment on 'unlock-on-merge' + implement auto unlock feature on pull request closure

- Update the `action.yml` file to include a new `unlock_on_close_mode` input
- Add a new file `unlock-on-close.js` with a function to release locks when a pull request is closed
- Update the `unlock-on-merge.js` file to include a reference to `lock metadata` and other related functions
- Introduce a new function `unlockOnClose` in the `main.js` file to run auto-unlock logic in the `unlock on close` mode

Author: xakraz

action.yml

@@ -133,8 +133,8 @@ inputs:
     description: This is an advanced option that is an alternate workflow bundled into this Action. You can optionally use this mode in a custom workflow to automatically release all locks that came from a pull request when the pull request is merged. This is useful if you want to ensure that locks are not left behind when a pull request is merged.
     required: false
     default: "false"
-  skip_completing:
-    description: 'If set to "true", skip the process of completing a deployment. You must manually create a deployment status after the deployment is complete. Default is "false"'
+  unlock_on_close_mode:
+    description: This is an advanced option that is an alternate workflow bundled into this Action. You can optionally use this mode in a custom workflow to automatically release all locks that came from a pull request when the pull request is closed. This is useful if you want to ensure that locks are not left behind when a pull request is closed.
     required: false
     default: "false"
   deploy_message_path: