[Workflow] Enforce TODO_UPNEXT comments to have an associated username

[Olshansk]

Summary

Improve process for TODO_UPNEXT

Goal is to block PRs on this: TODO_UPNEXT: <do something>
Allow PRs on this: TODO_UPNEXT(@olshansk): <do something>

Verification:

Issue

NA

Type of change

Select one or more from the following:

• New feature, functionality or library
• Consensus breaking; add the consensus-breaking label if so. See [Infra] Automatically add the consensus-breaking label #791 for details
• Bug fix
• Code health or cleanup
• Documentation
• Other (specify)

Testing

[Olshansk]

@okdas Is there easy way to test this without merging it in?

[okdas]

@okdas Is there easy way to test this without merging it in?

Yes - this PR can be used for testing. Just add TODO_UPNEXT: to any file.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
12819930	Triggered	Generic Password	203e76d	localnet/kubernetes/observability-prometheus-stack.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[bryanchriswhite]

Very cool. 😎

It would be nice if we could modify the comment contents to explain WHY it's complaining and what the author needs to change (i.e. add attribution). Perhaps it's out of scope but I'm wondering if that could be trivially possible via a different "reporter" or something?

(cc @okdas)

[Olshansk]

CCing @okdas and snoozing this email until next week.