fix: bump behavex from 3.2.0 to 4.0.9

[dependabot]

Bumps behavex from 3.2.0 to 4.0.9.

Changelog

Sourced from behavex's changelog.

Version: 4.0.9

ENHANCEMENTS:

• Adding support for latest Python versions (3.12)
• Performing cross-platform validations as part of github actions workflow (Linux, Windows and MacOS)
• Enabling adding scenario lines in feature paths when running BehaveX
• Fixing issue when performing dry runs, as internal @​BHX_MANUAL_DRY_RUN tag was not removed from the scenario tags

FIXES:

• Fixing execution issues in Windows OS when running BehaveX with a feature path different than the current path.
• Fixing encoding issues in progress bar in Windows OS

Version: 4.0.8

ENHANCEMENTS:

• Enhanced parallel scenario execution management by utilizing scenario lines over scenario names. This allows running scenarios that might change their name without causing issues in parallel executions.

FIXES:

• Avoid using the scenario name as part of the hash to generate output paths, as if the scenario name is changed, the path does not match. Instead, the feature filename and the line where the scenario is located is used to generate the hash.

Version: 4.0.7

ENHANCEMENTS:

• Improved KeyboardInterrupt handling when running BehaveX in parallel, by terminating all child processes before exiting.
• Simplified library documentation (README.md)
• Added more tests to validate BehaveX is working as expected when using latest stable Behave version (1.2.6)
• Adding the possibility to copy the scenario name in the HTML report

FIXES:

• Fix done when generating the features path (if not specified, BehaveX will use the current path as features path)
• Fix done when managing tags in scenario outlines
• Fix done when analyzing empty features
• Fix done to remove ansi color codes from the log files and HTML reporter (fd3c375 <https://github.com/hrcorval/behavex/commit/fd3c3756a13d9e47823f286022980e54e306d6da>_)

Version: 4.0.5

ENHANCEMENTS:

• Added the 'worker_id' context.config.userdata parameter to allow users to identify which worker is executing every feature or scenario when running tests in parallel. PR [#121](https://github.com/hrcorval/behavex/issues/121) <https://github.com/hrcorval/behavex/pull/121>_
• Adding the --parallel-delay argument, to enable setting a staggered execution when running tests in parallel. Issue [#142](https://github.com/hrcorval/behavex/issues/142) <https://github.com/hrcorval/behavex/issues/142>_

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)