ci: add --usecli when using --extended #34998

The current CI doesn't cover the case of running all tests with --extended if using --usecli. This led to a test failing (feature_index_prune.py) if run with --usecli and the CI not catching it. See #34991 for context.

This PR improves the CI test coverage by also running now all functional tests (--extended) with the flag --usecli. The CI obviously will fail in this PR until #34991 is merged into master.

~I don't know if this is the best approach; I just looked for a ci using --usecli and added the --extended flag to cover these scenarios.~ I'm open to changing the approach.

<!--e57a25ab6845829454e8d69fc972939a-->

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

<!--021abf342d371248e50ceaed478a90ca-->

Reviews

See the guideline for information on the review process. A summary of reviews will appear here.

<!--174a7506f384e20aa4161008e828411d-->

Conflicts

Reviewers, this pull request conflicts with the following ones:

• #34931 (validation: abort on DB unreadable coins instead of treating them as missing by furszy)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

<!--5faf32d7da4f0f540f40219e4f7537a3-->

Friendly pinging you here @fanquake

I think it would be better to pick one of the jobs already using --extended, and add --usecli.

I think it would be better to pick one of the jobs already using --extended, and add --usecli.

Done

I think the flag can now be removed from the other CI task

I think the flag can now be removed from the other CI task

Make sense, done :)

Closing because I have cherry picked this commit into the PR that is fixing the test that breakes this new CI behavior #34991