Publish using remote build and then local build Elastic Premium Linux

This doesn't work well, as remote build sets artifacts for the platform for "ExpressBuild" (aka remote build), which takes precedence over `WEBSITE_RUN_FROM_PACKAGE`. So, once remote build is done, it always takes over any other type of packaging.

This may be a bug well suited for kudu, however creating here to track.

No files, tests, or entry points are identified. Start by reproducing a publish that uses remote build followed by local packaging on Elastic Premium Linux, then trace how ExpressBuild artifacts take precedence over WEBSITE_RUN_FROM_PACKAGE and determine whether the fix belongs in these tools or Kudu. Done means both packaging modes work in the stated sequence.

Written by the indexing model from the issue text.