publish, connect - fix tar bundle creation using temp context

[cderv]

This PR fix the tar creation in bundle for connect.

The new function was not correctly handling filepaths, as the output tar is not in a relative place compared to the file to include, and also the tar creation command needs to be run in the same place as the file itself to be found

So now full path is used for files to include

[posit-snyk-bot]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[cderv]

While testing this, bundles creation is ok but there is an issue in how Posit connect deploy the bundle.

Somehow, the mimetype of the file is not correctly guessed it seems

dae6ae4-e701-461e-8627-484806458c91/:1 Refused to execute script from '<positserver>/content/bdae6ae4-e701-461e-8627-484806458c91/site_libs/quarto-nav/quarto-nav.js' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled

Is there something happening with this new tar library ?

[cscheid]

That's possible! One way to check is to create a tar file from the old version and compare it to the one created by the new version.

[cderv]

I found it, we've regressed on

• Correctly normalize to forward slash the path when creating tar.gz for Posit Connect deploys #8784 (which solved the exact same issue quarto publish connect from windows corrupts path delimiters in the bundle tar.gz #8749)

So I'll put back the normalization lost in refactoring.

[cscheid]

@cderv we should try to coordinate with the posit connect folks to have a scheduled integration test in CI.

[cderv]

Yes 💯 I already asked and they may have some solution we could run in CI. I'll update when I have something