Add test-suite from original (Dropbox's) Djinni repository

[freitass]

Adding tests for Java and Objective-C. The tests are located in the test-suite folder. “Djinni” code (enums, records and interfaces) for the test is generated from Djinni IDL at build time. The generated code is placed on the build directory.

Djinni version for code generation is specified in the tool-versions file. An alternative djinni command can be provided with the CMake option DJINNI_EXECUTABLE_PATH.

I’ve added a custom CMake command for the Djinni generator at test-suite/Djinni.cmake (I wonder if the generator project shouldn’t provide it instead).

[a4z]

I wonder what needs to be donethat the github action is actually executed for the PR.
It seems the current on: [push] does not trigger the build/test actions for a PR, or do I oversee something?

[freitass]

I was asking myself the same question. I thought there was some config on the repository that I could not see. The generator repo has this:

name: CI
on:
  push:
    branches:
    - '*'
  pull_request:
    branches:
      - main

Should we have the same?

[freitass]

Pushed minimal changes to have it run for the pull request.

[a4z]

awesome PR!