Add documentation for containerized native builds on remote daemons

[jonathan-meier]

Doc for PR #14635.

[zakkak]

Thanks for the PR @jonathan-meier :)
Please see my comments for a couple of typos and a suggestion.

[zakkak]

Suggested change

The reason for this is that the local build driver invoked through `Dquarkus.native.container-build=true` uses volume mounts to make the JAR available in the build container, but volume mounts do not work with remote daemons. The remote container build driver copies the necessary files instead of mounting them. Note that even though the remote driver also works with local daemons, the local driver should be preferred in the local case because mounting is usually more performant than copying.

The reason for this is that the local build driver invoked through `-Dquarkus.native.container-build=true` uses volume mounts to make the JAR available in the build container, but volume mounts do not work with remote daemons. The remote container build driver copies the necessary files instead of mounting them. Note that even though the remote driver also works with local daemons, the local driver should be preferred in the local case because mounting is usually more performant than copying.

[zakkak]

I suggest including a verbatim copy of the error. This way if people search for the error search engines will direct them to this tip.

[jonathan-meier]

Good suggestion, I reworded this part a bit to fluently include a copy of the error.

[zakkak]

Suggested change

	In this case, use the parameter `Dquarkus.native.remote-container-build=true` instead of `-Dquarkus.native.container-build=true`.
	In this case, use the parameter `-Dquarkus.native.remote-container-build=true` instead of `-Dquarkus.native.container-build=true`.

[jonathan-meier]

Thanks for the feedback! I fixed the typos and addressed your suggestion.

[zakkak]

Thanks for the fixes!

It looks good to me.

[gsmet]

Thanks!