Build(deps): bump mockable from 0.1.4 to 3.0.0

[dependabot]

Bumps mockable from 0.1.4 to 3.0.0.

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Labels

The following labels could not be found: cargo, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[leynos]

@coderabbitai please create a new GitHub issue for the following:

mockable v3.0.0 update is blocked due to a lint violation resulting from the upgrade:

Run make lint
RUSTDOCFLAGS="" cargo doc --no-deps
    Updating crates.io index
 Downloading crates ...
  Downloaded smart-default v0.7.1
    Checking xattr v1.6.1
    Checking filetime v0.2.27
   Compiling smart-default v0.7.1
    Checking tar v0.4.44
 Documenting podbot v0.1.0 (/home/runner/work/podbot/podbot)
warning: lint `missing_crate_level_docs` has been renamed to `rustdoc::missing_crate_level_docs`
  |
  = help: use the new name `rustdoc::missing_crate_level_docs`
  = note: requested on the command line with `-D missing_crate_level_docs`
  = note: `#[warn(renamed_and_removed_lints)]` on by default

warning: `podbot` (lib doc) generated 1 warning
    Finished `dev` profile [unoptimized] target(s) in 1.64s
   Generated /home/runner/work/podbot/podbot/target/doc/podbot/index.html
cargo clippy --all-targets --all-features -- -D warnings
   Compiling smart-default v0.7.1
    Checking podbot v0.1.0 (/home/runner/work/podbot/podbot)
error[E0599]: no function or associated item named `new` found for struct `mockable::DefaultEnv` in the current scope
Error:    --> src/main.rs:134:37
    |
134 |     let env = mockable::DefaultEnv::new();
    |                                     ^^^ function or associated item not found in `DefaultEnv`
    |
    = help: items from traits can only be used if the trait is in scope
help: trait `Paint` which provides `new` is implemented but not in scope; perhaps you want to import it
    |
13  + use yansi::paint::Paint;
    |

For more information about this error, try `rustc --explain E0599`.
error: could not compile `podbot` (bin "podbot" test) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
make: *** [Makefile:31: lint] Error 101
Error: Process completed with exit code 2.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

@leynos: I'll create a GitHub issue for this blocked upgrade.

---

🏁 Script executed:

#!/bin/bash
# Create a GitHub issue for the blocked mockable v3.0.0 update

gh issue create \
  --title "mockable v3.0.0 upgrade blocked by compilation errors" \
  --body "## Problem

The upgrade of \`mockable\` from version 0.1.4 to 3.0.0 is currently blocked due to compilation errors and lint warnings.

## Errors Encountered

### 1. Renamed Lint Warning
\`\`\`
warning: lint \`missing_crate_level_docs\` has been renamed to \`rustdoc::missing_crate_level_docs\`
  |
  = help: use the new name \`rustdoc::missing_crate_level_docs\`
  = note: requested on the command line with \`-D missing_crate_level_docs\`
\`\`\`

### 2. Missing \`new()\` Function
\`\`\`
error[E0599]: no function or associated item named \`new\` found for struct \`mockable::DefaultEnv\` in the current scope
  --> src/main.rs:134:37
    |
134 |     let env = mockable::DefaultEnv::new();
    |                                     ^^^ function or associated item not found in \`DefaultEnv\`
\`\`\`

The error suggests that the \`new()\` function is no longer available on \`mockable::DefaultEnv\` in version 3.0.0, indicating a breaking API change.

## Related

- PR: `#26`
- Reported by: `@leynos`

## Action Required

Investigate the mockable v3.0.0 API changes and update the codebase accordingly, particularly:
1. Update lint configuration to use \`rustdoc::missing_crate_level_docs\`
2. Update usage of \`mockable::DefaultEnv\` to match the new API" \
  --assignee leynos

Length of output: 42

---

@leynos: I've created issue #53 to track the blocked mockable v3.0.0 upgrade. The issue documents both the renamed lint warning and the missing new() function on mockable::DefaultEnv, and has been assigned to you.