NO-ISSUE: Fix dependencies 'replace' version

[ricardozanini]

Description of the change: Small changes to the mod files to avoid replacing the fixed v0.0.0 version to avoid conflicts between modules.

Motivation for the change: We only got this issue when trying to eliminate testbdd and bddframework modules in another PR. They did the replacement to all versions, whereas other modules would use v0.0.0. Additionally, testbdd was missing one dependency.

Checklist

• [ ] Add or Modify a unit test for your change
• [ ] Have you verified that tall the tests are passing?

How to backport a pull request to a different branch?

In order to automatically create a **backporting pull request** please add one or more labels having the following format `backport-`, where `` is the name of the branch where the pull request must be backported to (e.g., `backport-7.67.x` to backport the original PR to the `7.67.x` branch). > **NOTE**: **backporting** is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another. Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added. If something goes wrong, the author will be notified and at this point a manual backporting is needed. > **NOTE**: this automated backporting is triggered whenever a pull request on `main` branch is labeled or closed, but both conditions must be satisfied to get the new PR created.