Fixes #410: Add provider warnings

[abstractionfactory]

This PR adds the ability to include warnings for providers. This will translate to the (undocumented) "warnings" field in the V1 API response, which OpenTofu processes. This PR also marks all HashiCorp providers that are archived as deprecated, indicating an official replacement where found/available.

Fixes #410: Add provider warnings
Fixes #751: Deprecate maas/terraform-provider-maas
Related to: opentofu/libregistry#39

Example output in the versions response:

{
  "versions": [
    //...
  ],
  "warnings": [
    "This provider is deprecated."
  ]
}

[Yantrio]

I'll approve but im unsure about this failing check. It looks broken to me. can you look into it please @abstractionfactory ?

[abstractionfactory]

@Yantrio just checked, that one is indeed broken and should be removed. It tries to validate the /versions endpoint against a schema for the individual versions. Safe to ignore.

[tom-reinders]

@abstractionfactory Is not just the github action broken for multiple files?

This https://github.com/opentofu/registry/actions/runs/11287627799/workflow?pr=1123#L42 should just be

for path in ${CHANGED_FILES}; do

as per examples in actions README https://github.com/tj-actions/changed-files?tab=readme-ov-file#using-local-git-directory-

[abstractionfactory]

@tom-reinders I don't believe so, I checked the verification application and it doesn't actually work when passed a versions endpoint file.

[tom-reinders]

But the error in the action is trying to open all the files at ones in https://github.com/opentofu/registry/blob/main/src/cmd/validate/main.go#L93.
The only way for the validate command to get all path at ones in stead of seperated by the foreach is if the foreach is broken and it is.

[tom-reinders]

This

          for path in "$CHANGED_FILES"
          do
            /tmp/validate/run provider "$path"
          done

Does the same as this

/tmp/validate/run provider "$CHANGED_FILES"

Anything in between the " is 1 item in the foreach for path in "one path" "second path" and because the action is putting the full content of CHANGED_FILES in between the first set of " it sees it as one path.

[abstractionfactory]

So it's broken in more than one place. Wonderful. :D

[ollevche]

GitHub doesn't re-trigger provider validation because the latest commit has no changes to provider paths. Ideally, we would want to show final checks for the diff with the main (or other branch to merge to), because currently it is the way to bypass required validations.

Here is the throwaway commit to validate the check run just fine for this particular PR: https://github.com/opentofu/registry/actions/runs/11326232308/job/31494751924

[tom-reinders]

If you update the command to accept multiple paths than also update the command call in the GitHub action from

for path in "$CHANGED_FILES"
do
  /tmp/validate/run provider "$path"
done

to

/tmp/validate/run provider "$CHANGED_FILES"

to prevent people from making the mistake of thinking that the for loop really works what it does not.

[ollevche]

@tom-reinders makes sense! Here is the final run check: https://github.com/opentofu/registry/actions/runs/11326706265/job/31496187527

[tom-reinders]

LGTM!