One build method, one component manifest, bump version

[HermanPeeren]

There are currently two different methods in the repo to build a release of the component:

• JoRobo, with files jorobo.dist.ini, jorobo.ini (can leave out of repo, because this is the custom local version, if you need one; will add it to .gitignore), and RoboFile.php. If you have no package of multiple extensions (= a combination of the component with plugins and/or modules) then it takes the ccm.xml manifest file from the administrator folder of the component to copy it to the root of the component-zip.
• build scripts, with files build.php, and bump-version.php, called by the release.sh bash script. It uses the component_manifest.xml file to generate the manifest file in the root of the component-zip. It doen't change the ccm.xml manifest file that is already in the administrator folder of the component.

In the end I'd stick to JoRobo and delete build.php,bump-version.php,, release.sh, and component_manifest.xml.
Updated some things on ccm.xml manifest file in the administrator folder of the component in pr #58 .
Put the latest version of the component in your jorobo.ini file before running JoRobo.

**BUT: at the moment I have an error message when trying to build with JoRobo:

• ran into an error when using the bang behind "Joomla" with author = Joomla! Project in jorobo.ini
• cannot find deploy() method)

So we'll have to stick with two methods to build a release until JoRobo works for us (on Linux and Windows).

Used the script to build the release, copy-pasting the duplicate manifest; working on it,...
Also: in the current build-script the zip is made with a command, that doesn't work on Windows. I'll make it in PHP with ZipArchive (as is done in JoRobo in /Deploy/Package). I now zipped it seperately, not via the script.

There also is a script.php in the root of the repo, but it is targeted at a package. If you want a script when installing the component, you'd have to put that in the administrator side of the component. I left the script out of the v0.10.0 release.

[HermanPeeren]

Probably better: move to Github Actions for running tests, CI, build and deployment.

See for instance:

• run tests (in Weblinks): https://github.com/joomla-extensions/weblinks/actions/runs/17190597394
• run tests and build a release (in JA migration tool): https://github.com/joomla-projects/JA-Advanced-Migration-Tool/actions/runs/18040191326 . It is not yet completely good, but the way to do it is fantastic, really cool. 😎
• to build an release a component see for example https://github.com/N6REJ/n6rej.github.io/blob/main/Example%20workflows/component-packager.yml . More documentation: https://hallhome.us/joomla-packager/packager-documentation

Very interesting!