Identify usages in tests of State that can be replaced with key value instead

Problem/Motivation

There are tests that use the state service to determine whether a value was set as expected. Many of these usages are not testing the state service specifically, such as in 🐛 [random test failure] LayoutBuilderBlocksTest::testBlockPlaceholder failing Active . There are race conditions associated with state that can cause intermittent test failures. While the race conditions are being addressed in 🐛 Race conditions/bad lock logic in CacheCollector/State Active , using state in this cases should be replaced using key value storage directly.

This issue is to identify all the instances of stage usage that can be replaced. If the number of instances is small, then likely replacing them can all be done here as well. Or perhaps this issue can be converted to a meta with separate child issues to replace individual instances to break the work up.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet