ail-cli: does not automatically chmod +x the appimage file after moving it

[dreamcat4]

Describe the bug
ail-cli: does not automatically chmod +x the appimage file after moving it

Expected behavior
The moved appimage to be made executable. This expectation is a reasonable one, since AppimageLauncher has just made a .desktop file and must ensure that the file created is actually going to work. If AIL does not also auto chmod +x the appimage file, then that renders the installed application's .desktop file as broken. And it will fail to launch.

Since the whole goal of AIL program is to make easy and simle installation of appimage files. It should not assume that the input file was downloaded as being executable. Since it very well may not be.

To Reproduce

1. ail-cli integrate Olive-4cb02b67-x86_64.AppImage
2. try to open the new 'Olive' .desktop file. Nothing happens
3. Notice that the installed appimage file is not executable, even after it has been moved to the install location by ail-cli program
4. chmod +x the installed appimage file
5. Try to open via installed .desktop file again

System, software and AppImage information

ubuntu 19.10, appimagelauncher (202003070416-stable-e405182~ubuntu19.10.1) was installed via APT repo, like this:

https://gist.github.com/dreamcat4/8a3b4d84e746231dfc8250a49a259a68

List of AppImages you tried:

• olive

[WeMakeMachines]

I can confirm this issue also happens to me, when trying to install KDevelop via the ail-cli integrate ./KDevelop.AppImage

It moves the file into the ~/Applications directory, but a quick ls -l on that folder shows the moved file is missing permissions to execute

If I use the GUI with the option "Integrate and run", it works fine

[InklingGirl]

Having the exact same issue as @dreamcat4 & @WeMakeMachines to a T. I swear it used to work, too. This should really be addressed, because ail-cli was really helpful for automating the deployment of AppImages & I'd rather not have to write the duct tape myself.