ci(getblocktemplate): run getblocktemplate-rpcs feature tests in CI

[oxarbitrage]

Motivation

One option for #5405 is to run a new test task with the getblocktemplate-rpcs feature enabled.

Solution

Run a new task with getblocktemplate-rpc feature enabled. This will run the tests with and without the feature in a separated task for each case. I think is what we want to make sure everything pass when the feature is enabled/disabled in addition to run extra tests when enabled.

New tests can be seen in the logs at:
https://github.com/ZcashFoundation/zebra/actions/runs/3291277916/jobs/5425229470#step:15:4896
https://github.com/ZcashFoundation/zebra/actions/runs/3291277916/jobs/5425229470#step:15:4912

Review

Reviewer Checklist

• Will the PR name make sense to users?
  • Does it need extra CHANGELOG info? (new features, breaking changes, large changes)
• Are the PR labels correct?
• Does the code do what the ticket and PR says?
• How do you know it works? Does it have tests?

Follow Up Work

[teor2345]

Looks good, can you also run the Zebra tests on Docker with this feature?
Docker is our main supported platform, so it needs these tests as well.

zebra/.github/workflows/continous-integration-docker.yml

Line 195 in f31609e

- name: Run all zebrad tests

I checked the other workflows:

Lint and build crates individually already run with all features. I don't think we need to run the lightwalletd integration tests, coverage, or parameter downloads with this feature.

[oxarbitrage]

Docker logs of getblockcount tests:
https://github.com/ZcashFoundation/zebra/actions/runs/3300655521/jobs/5445883887#step:3:4140
https://github.com/ZcashFoundation/zebra/actions/runs/3300655521/jobs/5445883887#step:3:4156

[teor2345]

Looks good!

I think we might want to run both sets of tests, with and without the new feature. (We can stop doing that when the new feature is on by default.)

[teor2345]

Thanks, looks great!