🌱 Add lifecycle field to probes

[spencerschrock]

What kind of change does this PR introduce?

structured results update

• PR title follows the guidelines defined in our pull request documentation

What is the current behavior?

There is no indication around whether a probe can be depended on or not. And there are examples of probes being removed (#3666 and #3559 (comment))

What is the new behavior (if this is a feature change)?**

Clearly mark if a probe is:

• experimental (the semantics of the probe may change)
• stable (the probe behavior and semantics should remain stable, there may be bug fixes as needed)
• deprecated (the probe doesn't receive further updates)

• Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes

NONE

Special notes for your reviewer

Does this PR introduce a user-facing change?

For user-facing changes, please add a concise, human-readable release note to
the release-note

(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

NONE

[spencerschrock]

This PR marks all probes as stable, except for the following:

• codeReviewOneReviewers: Because it's not being used by a check and hasn't been thoroughly viewed.
• All of the token permission probes, as the semantics may not be final
  • topLevelPermissions:
  • jobLevelPermissions
  • hasNoGitHubWorkflowPermissionUnknown
• probes which are still in active development or belong to experimental checks:
  • hasReleaseSBOM
  • hasSBOM
  • releasesHaveVerifiedProvenance
  • webhooksUseSecrets
• probes which may have significant bugs in their behavior
  • contributorsFromOrgOrCompany

[github-actions]

This pull request has been marked stale because it has been open for 10 days with no activity