[ci] deprecated jail field in release test definition

[can-anyscale]

Why are these changes needed?

Currently the test can be jailed via two ways, either through this 'jailed' field in test definition, or by test state machine. Deprecated this jailed field and let the state machine does it job. This refuses confusion around how to unjail and jail a test.

Also improve the logic of soft fail and append the [jailed] to the buildkite step name. We should not soft fail when the test is jailed.

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• Testing Strategy
  • Unit tests
  • Release tests

[can-anyscale]

Check that https://buildkite.com/ray-project/release-tests-pr/builds/42882 the jailed test runs correctly and the step name is denoted with [jailed]

[aslonnie]

how can one easily tell what is the current state of a test now?

[can-anyscale]

@aslonnie through github issue i guess go/release-test

[can-anyscale]

@rickyyx fyi, this removed the jailed test feature from release test definition, and rely sole on the test state machine to jail test. Should not change the behavior of your existing jail test significantly.

[rickyyx]

@rickyyx fyi, this removed the jailed test feature from release test definition, and rely sole on the test state machine to jail test. Should not change the behavior of your existing jail test significantly.

So unstable tests will still be running right?

ray/release/release_tests.yaml

Lines 4757 to 4758 in b9ef5da

	stable: false
	jailed: true

[can-anyscale]

@rickyyx that's right, they will still be running