chore(deps): update docker/login-action action to v3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
docker/login-action	action	major	v2 -> v3

---

Release Notes

docker/login-action (docker/login-action)

v3

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[richardli1598]

Hello, I am a code review bot on flows.network. Here are my reviews of changed source code files in this PR.

---

The patch applies an update to the Docker login-action from version 2 to version 3. Here are the areas that need attention:

1. Check compatibility: The migration from docker/login-action@v2 to docker/login-action@v3 should be checked for compatibility with the rest of the workflow. Ensure that there are no breaking changes in the action's usage between these versions that would affect the workflow.

2. Update action parameters if needed: With the version update, there might be changes to the inputs or outputs of the login-action. Review the release notes or documentation of docker/login-action@v3 to verify if any changes are needed in the with block that provides username and password.

3. Test the workflow: After updating the action version, it's crucial to test the workflow to confirm that the Docker Hub login functionality works as expected. This might involve running the workflow in a test environment or ensuring that you have proper monitoring on the initial deployments after the update.

4. Check for updates in other related actions: If docker/login-action has been updated, there might be updates available for related actions such as docker/setup-buildx-action. Although it is already using v3, it might be a good practice to regularly check if there are new versions for other actions in use.

5. Documentation and changelog: If maintaining documentation or a changelog for the project, the update should be recorded, noting the version change and the reason (e.g., to incorporate new features, security improvements, or bug fixes).

In the provided diff snippet, there do not appear to be any syntax errors or issues directly related to the changes made. The patch solely updates the version of docker/login-action in three distinct GitHub action workflow files, and does not modify any other lines of code or workflow logic. However, without testing the actual workflows and confirming the non-breaking nature of the update, it is not possible to guarantee that these changes are safe to merge.

[netlify]

✅ Deploy Preview for kubespider ready!

Name	Link
🔨 Latest commit	59ecf2a
🔍 Latest deploy log	https://app.netlify.com/sites/kubespider/deploys/65815f62086f9700086c5d11
😎 Deploy Preview	https://deploy-preview-429--kubespider.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.