Separate binding code into individual module-specific bindings

[seungsoo47]

This change is a refactoring effort to modularize the tizen_interop binding structure, improving code management and maintainability.

• Refactored the monolithic binding code into separate and independent binding codes for each Tizen 6.0 API module.
• Created separate entrypoint header files & ffigen configuration files for each Tizen API module
• Generated separate binding code for each Tizen 6.0 module.
• Fix helper script bugs.
• Add missing headers and libraries in tizen 6.5 and 9.0.

[gemini-code-assist]

Code Review

This pull request is a significant refactoring to modularize the FFI bindings, which greatly improves maintainability. The changes in the integration tests correctly reflect this new modular structure. I've found one minor issue in the test logic for error handling which should be addressed.

[JSUYA]

I tried to create 6.5 bindings based on this PR.
However, I believe a script should be provided that allows running scripts/ffigen_helper.sh 6.5 to generate ffigen-*.yaml in a basic format, similar to 6.0. Please let me know if I am missing anything.
I think the structure should allow other users to create new version bindings without issues and easy by following the guide.

[seungsoo47]

I tried to create 6.5 bindings based on this PR. However, I believe a script should be provided that allows running scripts/ffigen_helper.sh 6.5 to generate ffigen-*.yaml in a basic format, similar to 6.0. Please let me know if I am missing anything. I think the structure should allow other users to create new version bindings without issues and easy by following the guide.

As we discussed offline, we will be able to provide the script later.