Resolve discrepancy between publish CI and release-please

I was surprised to find that, after merging the release-please PR, it created a tag by the name `bevy_pipe_affect-v0.1.0`, not just `v0.1.0`. Some CI for publishing was assuming that it would be the latter, so I ended up making that tag myself. This issue is for resolving this discrepancy, which could mean adjusting the assumption or the release-please config.