[bug v2] AppImage update doe not set execute permission on file

[mildred]

Describe the bug

When updating an AppImage, it downloads the new version and does copy it in place of the old executable, but the new AppImage is not given the execute permissions and when restarting the application, it cannot start due to lack of execute permissions

a chmod +x is required on the new AppImage file

it seems missing from

plugins-workspace/plugins/updater/src/updater.rs

Line 763 in f83b9e9

fn install_inner(&self, bytes: &[u8]) -> Result<()> {

Reproduction

Run the update process with an AppImage on Linux

Try to open https://github.com/mildred/web_docs/releases/tag/v0.1.3 and perform the update. It won't restart automatically due to lack of permissions, but restarting manually should show the issue.

Expected behavior

it should work

Full tauri info output

[✔] Environment
    - OS: Fedora 40 X64
    ✔ webkit2gtk-4.1: 2.44.2
    ✔ rsvg2: 2.57.1
    ✔ rustc: 1.79.0 (129f3b996 2024-06-10)
    ✔ cargo: 1.79.0 (ffa9cf99a 2024-06-03)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 22.4.1
    - yarn: 1.22.22
    - npm: 10.8.1

[-] Packages
    - tauri [RUST]: 2.0.0-beta.24
    - tauri-build [RUST]: 2.0.0-beta.19
    - wry [RUST]: 0.41.0
    - tao [RUST]: 0.28.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.15
    - @tauri-apps/cli [NPM]: 2.0.0-beta.22

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Rollup

### Stack trace

_No response_

### Additional context

_No response_

[ktecho]

It happens here too (Linux / AppImage), but I get this while trying to update:

ktecho@lggram:~$ ./resurrection_wallet_0.3.0_amd64.appimage 
thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-2.0.0-rc.0/src/process.rs:82:8:
application failed to start: Os { code: 13, kind: PermissionDenied, message: "Permiso denegado" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Abortado (`core' generado)

"Permiso denegado" is "Permission denied".

Maybe it fails to change the u+x and that's why it cannot be re-executed again?

[amrbashir]

fixed by #1636