hotfix: cherry pick integration test fix for scheduled runs

[rflechtner]

fixes #504

As far as I can see the only issue leading to failure in our weekly run with updated deps is that the integration tests are out of sync with the latest chain runtime. This should take care of the problem.

[ntn-x2]

LGTM! Unfortunately, the merging of KILTprotocol/kilt-node#316 into develop means that integration tests now are again broken, because something changed in the storage layout. It is definitely not to be fixed in this PR, but I guess we will keep having problems as long as the issue is not fixed, or as long as we can't safely ignore the result of testing against latest-develop.

[rflechtner]

LGTM! Unfortunately, the merging of KILTprotocol/mashnet-node#316 into develop means that integration tests now are again broken, because something changed in the storage layout. It is definitely not to be fixed in this PR, but I guess we will keep having problems as long as the issue is not fixed, or as long as we can't safely ignore the result of testing against latest-develop.

Technically the tests against latest-develop are optional, so this may hit us only later when these changes are released - although the GitHub Actions status has behaved somewhat inconsistently in the past