ci: revert back to previous logic of adding ownership to crates.io

[Mossaka]

I've done some experiments with cargo owner --add command and apparently that the bot (containerd-runwasi-release-bot) is not able to add github:containerd:runwasi-committers as an owner to the published crate by itself. See https://github.com/containerd/runwasi/actions/runs/6711072386/job/18237873816#step:8:13

However, the bot was able to add the user who triggered the action as an owner to the published crate. See: https://github.com/containerd/runwasi/actions/runs/6714433126/job/18247647749#step:3:26

I want to revert the change back to previous logic to first examine if this published crate already has the desired owner. Otherwise, it adds the user who triggered the action as an owner and the user has then to add github:containerd:runwasi-committers as an owner. This follows the doc in RELEASE.md.

The branch add-owner serves the single purpose of adding myself as an owner to the published containerd-shim-wasm-test-modules crate so that I can add runwasi-committes to its owners. I will delete this branch shortly after.

[Mossaka]

Could you please review this PR? @jsturtevant @jprendes

[cpuguy83]

I think if we add the bot to the committers group it should be able to work.
Most likely since it is not part of the group it can't even see the group.

[jprendes]

I think this is the same error message as in
rust-lang/crates.io#3031

[Mossaka]

@cpuguy83 can you do that for the bot account? I assume that only you have the crendentials for it.

[cpuguy83]

I'll take a look.
I think we'll also need to login as the release bot in CI.