Refactor `CONDUCT.md`:

[jpmcb]

From the CONDUCT.md:

Deprecation of Go versions or dependent packages will only occur in major releases.

It's been awhile since I read that deprecation policy but I'm not sure I agree with it anymore: we should in theory be able to drop "supported" versions of our dependencies without having any breaking changes to the core functionality of cobra. People could still use cobra without issue it just wouldn't be "supported".

...

It'll never be sustainable for us to make major releases with how fast Go deprecates it's versions.

Originally posted by @jpmcb in https://github.com/spf13/cobra/pull/1783#discussion_r966143826

---

It's time we revisited the conduct and current community agreement. Pr to come!

[umarcor]

Context: https://github.com/spf13/cobra/issues/1232

[github-actions[bot]]

The Cobra project currently lacks enough contributors to adequately respond to all issues. This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied. - After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can:
• Make a comment to remove the stale label and show your support. The 60 days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening

[tlarnold10]

@jpmcb want some help with this? I can take a shot at it depending what you are looking for.