Enable dependabot for github actions again?

[mateusoliveira43]

Describe the problem/challenge you have

Saw this PR #6622 and wondered why dependabot for GitHub Actions was removed (it even opened a PR for that change #5546). Would it not be good for automating these changes?

Describe the solution you'd like

Enabling dependabot again for these situations.

Anything else you would like to add:

Did not find any issues/discussions about disabling dependabot for GitHub Actions, please add them (if any).

Environment:

• GitHub Actions

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "The project would be better with this feature added"
• 👎 for "This feature will not enhance the project in a meaningful way"

[blackpiglet]

Needs more input from other contributors on this topic.
My feeling is that dependabot will create PR immediately when there is a new version available, and reviewers don't know what is the benefit and whether there is a side-effect of the change.
Although the two mentioned PRs have similar changes, the manually created one is used to address some issues we met.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions]

This issue was closed because it has been stalled for 14 days with no activity.