fix: some URLs updated from "intel" to "ossf" are now broken

[alex-ter]

In #5455 many links were updated, and rightfully so. I haven't had time to review in detail back then. I took a look now and caught a couple of URLs that either should have not been updated or require an additional action.

1. The codecov.io one (this line in the diff). I can't seem to access the project under "ossf" (the "intel" one is still visible), and the badge URL returns one with "unknown" coverage, so it seems to me the "ossf" one doesn't exist.
   1. I guess the action here would be to do the needful at the codecov.io side to either migrate the old project or create the new one.
2. The cve-bin-tool action repo. It wasn't migrated (yet?), so the update (at least here and here) was a bit premature.
   1. Here my suggestion would be to actually migrate the repo under OpenSSF, as it only makes sense, as a part of the whole cve-bin-tool package.

So in both cases I guess the changes can stay, but some additional action is required to make them work. I'm afraid I can't act on either of those due to not being the maintainer to represent the project (the latter) or having access to the codecov.io (the former), though let me know if you think otherwise, so just drawing your attention here.

[alex-ter]

@terriko, @anthonyharrison, @ffontaine, or maybe even @ware (as you were involved in the move) - do you know if the second point above (leaving the cve-bin-tool action repo behind) was intentional or just an omission that should probably be rectified?

[ffontaine]

I would assume that this is an omission but fixing it would probably take a (very) long time

[terriko]

Hey @alex-ter -- sorry about the delay. You'll have to ask Intel about what they want to do with the -action repo. I believe I told them that they could move it, but in the chaos of everything I'm not surprised if one or more of us forgot. I'd suggest we just fork and keep going if we intend to maintain it. I do not intend to maintain it myself; as you've seen, moving and starting a new job has been all-consuming so I'm down to maybe 2 hours/month that i can dedicate to cve-bin-tool right now.

[terriko]

For codecov, yeah, I htink we need to make a new codecov account. Feel free, I think anyone can do that since I did it on a day when I didn't have admin access to the cve-bin-tool repo anyhow.

[alex-ter]

@terriko, Thanks Terri and glad to have you back, in whatever capacity! I'll see about creating the codecov account and on the Action side - do you think we could fork it to the ossf organization or that would rather be under someone's personal account, at least for starters? I could do that as well, if the latter.