Enhancement: confirm buttons

[shamoon]

Proposed change

Small UI thing that came up in #5190 (and this PR is dependent on that just so the changes there are included). This adds a little confirmation to certain buttons in the UI. Eg:

Edit: I've narrowed down the scope of this PR, the button is used for:

• Profile regenerate API key and disconnect social account
• Workflow editing delete action and trigger (currently has no confirm)
• Saved view delete (this actually had no confirm before, which seems inconsistent)

Closes #(issue or discussion)

Type of change

• Bug fix: non-breaking change which fixes an issue.
• New feature / Enhancement: non-breaking change which adds functionality. Please read the important note above.
• Breaking change: fix or feature that would cause existing functionality to not work as expected.
• Documentation only.
• Other. Please explain:

Checklist:

• I have read & agree with the contributing guidelines.
• If applicable, I have included testing coverage for new code in this PR, for backend and / or front-end changes.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• If applicable, I have checked that all tests pass, see documentation.
• I have run all pre-commit hooks, see documentation.
• I have made corresponding changes to the documentation as needed.
• I have checked my modifications for any breaking changes.

[shamoon]

I've narrowed down the scope here.

[stumpylog]

Maybe just to be cleaner, you could drop the extra commits?

[shamoon]

I dont know if I can now that theres a merge commit, but when this is merged in it'll get squashed cleanly to the one commit, right?

[stumpylog]

It probably will. I guess just make sure the co-authored isn't set?

[shamoon]

Or I can open a new PR if you prefer

[shamoon]

Yea, should be clean I think?

[shamoon]

I'm just gonna open a new PR...

[shamoon]

Ok sorted, sorry for the noise

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns. See our contributing guidelines for more details.