✨ Enable users to integrate external checks via blank-imports

[johnandersen777]

What kind of change does this PR introduce?

• feat: expose checker registration
• feat: enable checker go plugins
• feat: docs for checker go plugins
• feat: tests for checker go plugins
• PR title follows the guidelines defined in our pull request documentation

What is the current behavior?

• Checks must be added in tree within upstream scorecard repo

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

• Plugins can be loaded by specifying a SCORECARD_DYNAMIC_CHECKS
  environment variable which leverages Golang plugins
• Docs have been added
  • [ ]
• Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes

NONE

Special notes for your reviewer

TODO

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.)

Check plugins using go plugins

[johnandersen777]

• Rename to checks/plugins.go

[spencerschrock]

We are trying to avoid using plugins for the reasons specified in #3095

[spencerschrock]

cc @naveensrinivasan for possible coordination

[johnandersen777]

Thanks @spencerschrock, so just to clarify focus of this PR would be on the check docs side of things?

[spencerschrock]

Thanks @spencerschrock, so just to clarify focus of this PR would be on the check docs side of things?

There's still the aspect of the changes outlined in #3095, and the followup comment #3095 (comment).

[github-actions]

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

[naveensrinivasan]

I apologize for the delayed response. I will be working on this. Thanks!

[johnandersen777]

Should I close this PR then?

…

On Wed, Feb 7, 2024 at 11:40 Naveen ***@***.***> wrote: I apologize for the delayed response. I will be working on this. Thanks! — Reply to this email directly, view it on GitHub <#3809 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNMXYMCNICMJJ6J56Q5ENDYSPKCXAVCNFSM6AAAAABCA4DPX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZSG42DIMBRGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[spencerschrock]

Should I close this PR then?

I'm not sure about Naveen's expected timeline, but I'll go ahead and close this for now.
@naveensrinivasan can you update us if you dont end up pursuing this?