Update @vardot/varbase-e2e to 2.0.6 and make the step timeout actually take effect

Problem/Motivation

@vardot/varbase-e2e 2.0.6 is released. It fixes smartSettle waiting forever on a page whose network never goes idle, which showed up as a bare function timed out after 45s.

Two things in this project need attention with it. The timeout: 60000 in cucumber.js has no effect, because varbase-e2e's own setDefaultTimeout() overrides the config key, so the suite has been running on 45s. And the 📊 Create reports job installs varbase-e2e with no version at all.

Proposed resolution

Raise the floor in package.json to ^2.0.6, pin the report job's install to the same floor, set the step timeout through VARBASE_E2E_STEP_TIMEOUT, and guard the functional job's report step so it prints one line instead of a stack trace when the tests never ran.

Remaining tasks

• ✅ Update the version floor and the CI pin
• ✅ Make the step timeout take effect
• ✅ Guard the report step
• ❌ Code review by maintainers

User interface changes

• None.

API changes

• None.

Data model changes

• None.

Release notes snippet

• Updated the Varbase functional testing suite to @vardot/varbase-e2e 2.0.6, and fixed the step timeout in cucumber.js, which had no effect.

AI-Generated: Yes