Update bridges integration-tests instructions

[bkontur]

This PR adjusts the instructions on how to run bridges integration tests.

• [X] Does not require a CHANGELOG entry

Future improvements: https://github.com/paritytech/parity-bridges-common/issues/3016

[bkontur]

/merge

[fellowship-merge-bot[bot]]

Enabled auto-merge in Pull Request

Available commands

- `/merge`: Enables auto-merge for Pull Request - `/merge cancel`: Cancels auto-merge for Pull Request - `/merge help`: Shows this menu For more information see the [documentation](https://github.com/paritytech/auto-merge-bot)

[bkontur]

Looks quite complicated and also raises the question why you need the sudo pallet with fast runtime? Let's merge this, but would be nice to improve this.

Yes, you're right. That's why I created issue #3016. When we started with the zombienet bridges tests, preopen_hrmp stopped working at some point (more info). As a workaround, I used force_open_hrmp_channel because establish_system_channel didn't exist at that time. Sudo is needed for the init-bridge governance call from the relay, but that could probably be replaced with a genesis setup or with Chopsticks and governance call.

[fellowship-merge-bot[bot]]

Failed to update PR ❌

There was an error while trying to keep this PR up-to-date

You may have conflicts ‼️ or may have to manually sync it with the target branch 👉❇️

More info in the logs 📋

[fellowship-merge-bot[bot]]

Failed to update PR ❌

There was an error while trying to keep this PR up-to-date

You may have conflicts ‼️ or may have to manually sync it with the target branch 👉❇️

More info in the logs 📋

[fellowship-merge-bot[bot]]

Failed to update PR ❌

There was an error while trying to keep this PR up-to-date

You may have conflicts ‼️ or may have to manually sync it with the target branch 👉❇️

More info in the logs 📋