Re-enable builds on github action using arch linux container environment

[naokiri]

Suggested fix on the last comment of #83

TODO: Need to review and confirm the release file actually works before merging. Run with workflow_dispatch event and fix the release file not to be attatched to the release but to be downloadable on manual run

[naokiri]

Current issue: library path problem

On Archlinux and most fcitx5 development environment (= the new build env) -> uses source builds and saves RPATH on build, so they can find the shared libraries.

On deb file I'm making -> I want to make it able to use with latest Ubuntu at least as large portion of JP Linux users use that distribution. They expect fcitx5 libraries to be under /lib/x86_64-linux-gnu/fcitx5/ so making the deb file to distribute this lib to that directory even though it is usually for system's package managers' directory.

CSKK -> The deb file on release places the libcskk under /usr/local/lib/cskk as it is not expected to be the system's library but more like a local build library.

For these mixed up pathes especially the RPATH stored on the build time, the library search paths are mixed up and not easy to confirm what library is actually missing or just unable to find from the search paths or accidentally finding the old version.

Storing RPATH on build was an easy fix for using non-system library like CSKK but it causes more trouble when we want to run on multiple environments and expecting different build environment and runtime environment.

We probably need to disable storing RPATH and find a better solution for locally built libraries.

[naokiri]

Even if I fix the library resolution PATHs, making a good deb file for Ubuntu24 seems hard because fcitx5 have changed the ABI and now we are building against latest fcitx5 which uses FCITX_ADDON_FACTORY_V2, but the Ubuntu's fcitx5 package only accepts FCITX_ADDON_FACTORY version.
Being able to build with newer fcitx5 is important as wayland is evolving fast these days, but if I want to support most of the JP users I have to retain the old code.

[wengxt]

Even if I fix the library resolution PATHs, making a good deb file for Ubuntu24 seems hard because fcitx5 have changed the ABI and now we are building against latest fcitx5 which uses FCITX_ADDON_FACTORY_V2, but the Ubuntu's fcitx5 package only accepts FCITX_ADDON_FACTORY version. Being able to build with newer fcitx5 is important as wayland is evolving fast these days, but if I want to support most of the JP users I have to retain the old code.

you can still use FCITX_ADDON_FACTORY, that's no problem. If you want , you could do ifdef check to prefer FCITX_ADDON_FACTORY_V2 where possible