Test trigger doesn't use the latest commit on master

[thunderbiscuit]

Looking at this test run, you can see that the CI pulls the latest commit in the "Update bdk-ffi submodule to latest" task, but then the build script itself performs a git submodule update --init in the "Run JVM tests" task.

The result is that the tests are run against the committed version of bdk-ffi, not the latest commit on master.

Logs:

# Early in the run
Testing commit: 8496e53 fix(kyoto): Remove the `Debug` logs from public API (author: GitHub)

# Later on
Submodule check...
Submodule path 'bdk-ffi': checked out '5ef6134440e711bf1be57b7a0a33f54ffb5185e5'
Submodule is checked out at commit:  5ef6134440e711bf1be57b7a0a33f54ffb5185e5 bdk-ffi (v0.28.0-rc.0-541-g5ef6134)

[thunderbiscuit]

A sub-issue is the fact that I used the "committer" in the string rather than the "author", which can give you things like you see above (author: GitHub when it was actually rustaceanrob who wrote the commit). I'll fix that.

EDIT: I actually just sneaked it in my PR #18... 😆

[ItoroD]

oh wow. I never knew when git submodule update --init was added in build script. I would probably never have guessed it.