AppBundler v1.0

[JanisErdmanis]

This pull request focuses on bringing AppBundler to a 1.0 release. The primary goals are to stabilise the API and write corresponding documentation that makes AppBundler's functionality accessible to users.

It has become clear that AppBundler could, in the future, serve other programming language ecosystems such as Rust, Go, and Python, which currently rely on host system utilities for bundling and could therefore benefit from cross-platform bundling to significantly simplify deployment maintenance. With this in mind, the coupling between JuliaC and JuliaImg modules needs to be reworked so that they function more like extensions rather than integral parts of the AppBundler project. JuliaImg, for instance, could be worth investigating as a self-contained package.

Regarding API changes, this release will transition to using Preferences.toml as a more future-proof approach. There is also work to be done in evaluating each parameter name and potentially consolidating them along the way.

The following tasks need to be completed for this PR:

• Revise API naming and implement Preferences.toml
• Set up Documenter and document the API
• Fix Julia 1.12 support ([#20](Julia 1.12 support #20))
• Fix security issue with the run command ([#28](Security suggestion: avoid exposing sensitive information in CI logs #28))

[JanisErdmanis]

The API for preferences is now finalised. I have tested it on all examples and some larger projects on macOS. Some tests yet need to be performed on Windows and Linux before the 1.0 release.

To address security issue #28, AppBundler could consume the secrets via standard input, as discussed here: https://utcc.utoronto.ca/~cks/space/blog/programming/PassingSecretsViaStdin. This approach would ensure that the secrets are not listed within environment variables at all. Need to check, though, whether Windows Shell has a piping operator I can rely on.

[JanisErdmanis]

Security issue #28 is about to be fixed. I decided to adopt a strategy where passwords can be passed as command-line arguments, with stdin as the default when absent. Although passing a password as a command-line argument is not safe on local systems, where one can explore processes, it could be considered rather safe on CI like GitHub or GitLab, which do not expose process exploration.