Reduce the number of CI runs for older EVM versions

[cameel]

1. Move constantinople and petersburg runs to nightly

Since we are planning to remove support for ancient EVM versions in 0.9.0, some time ago we decided to run tests on those versions only in the nightly workflow (#14710). However, this was done only for the two oldest ones (homestead and byzantium). To further reduce our CI cost we could move constantinople and petersburg as well.

2. Replace t_ubu_soltest_all with t_ubu_soltest

Most of our testing in CI in done is by the _soltest jobs, which run on the current EVM version, but we also have two _soltest_all runs for more thorough coverage: t_ubu_soltest_all and t_ubu_force_release_soltest_all. These run tests on all non-deprecated EVM targets.

The difference between the two is minimal: t_ubu_force_release_soltest_all has a proper release version, which can matter in some situations, but does not affect most things. The biggest value it adds is just before release, because it may let us spot problems that would only show up on a tagged commit. I think we can safely replace t_ubu_soltest_all with t_ubu_soltest. Doing a full run on a release binary gives us enough information.

[manuelwedler]

done in #16353 and #16350