Multi-arch container publishing doesn't work when certain RID-forcing publish properties are set

### Describe the bug

See [this Bluesky thread](https://bsky.app/profile/chrismckee.bsky.social/post/3lunqvhetjs2j) for context and discussion.

With multi-arch container publish being a thing, some users are using it with publish configurations that conflict with historical decisions that the .NET SDK has had. Specifically, while we would like the container publish for multi arch to logically look like

* outer build does zero work
* triggers N inner RID-specific build
* outer build uses results of inner build to make image manifest

The decision to make the `PublishContainer` target implicitly rely on the `Publish` target (via the documented command `dotnet publish -t:PublishContainer`) means that the outer project (with no RID set) is also asked to publish - and as a result if the outer project has properties like `PublishReadyToRun`, `PublishAot`, etc set then the RuntimeIdentifierInference targets force it to get a RID, which then short-circuits the decision-making of the PublishContainer target on if it is doing multi-arch publish.

One workaround is to disable `UseCurrentRuntimeIdentifier`, but the CLi today seems to not allow passing `false` for this option.