Do not use constraints from bazel_tools

[limdor]

Fixes #1953

PR Checklist

Please check if your PR fulfills the following requirements:

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

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

Does this PR introduce a breaking change?

• Yes
• No

[gravypod]

Hello @limdor. This change looks good but I'd like to know: is there a reason this needs to be done? I'm assuming this blocks some migration or deprecation in bazel_tools or something. I just want to know what to tell future people if they ask about this change.

[gravypod]

Ah, I just saw the attached bug! Thanks for putting this together.

[limdor]

@gravypod it seems that I'm the first one seeing this but this is needed to be able to compile with Bazel 5.0. It would be good if a release could be created soon that contains this changes. Without it rules_docker cannot be used in Bazel 5.0.
The good part is that with this changes works for Bazel 5.0 but it also keeps working for Bazel 4.x