Releasability check flags GO when it shouldn't

Not sure where I have to open this, so I'll open here:

> There is a bug in the automation that flagged some repos as ready to be cutted [6] but they were not [7], because pointing at the wrong eventing release. There is a similar bug that happened to eventing-awssqs, making it depend on hack master because it was an indirect dependency.

[6] https://github.com/knative-sandbox/eventing-natss/actions/runs/480133288
[7] https://github.com/knative-sandbox/eventing-natss/commit/6a1c1d999e1964327b72189d2c17ecf121498208#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6R21

From https://groups.google.com/g/knative-dev/c/jQsloZD-sW8/m/8E31LeFGCgAJ

Start by inspecting the linked GitHub Actions run and the referenced eventing-natss commit, especially the diff location identified at line 21. Trace why the releasability check points at the wrong eventing release and treats an indirect dependency as hack master. Done means affected repositories are not flagged GO until their actual dependency releases are ready.

Written by the indexing model from the issue text.