build(deps): update craft-application and craft-providers (canonical#2069)

Use a unique build environment for each platform in a charm recipe.

### Scenario 1

* Fixes a bug where multiple platforms would build in the same build
environment if the platforms had the same `build-on` and `build-for`
entries.

```yaml
platforms:
  noble:
      build-on: [riscv64]
      build-for: [riscv64]
  noble-debug:
      build-on: [riscv64]
      build-for: [riscv64]
```

###  Scenario 2

* Improves build time for multi-base recipes. Previously, Charmcraft
would tear down and recreate the same container when building for a
different base if the platforms had the same `build-on` and `build-for`
entries.

```yaml
platforms:
  jammy:
      build-on: [[email protected]:riscv64]
      build-for: [[email protected]:riscv64]
  noble:
      build-on: [[email protected]:riscv64]
      build-for: [[email protected]:riscv64]
```


Fixes canonical#2058 
(CRAFT-3847)

Signed-off-by: Callahan Kovacs <[email protected]>

Author: mr-cal

pyproject.toml

@@ -4,11 +4,11 @@ dynamic = ["version"]
 description = "The main tool to build, upload, and develop in general the Juju charms."
 readme = "README.md"
 dependencies = [
-    "craft-application~=4.7",
+    "craft-application~=4.8",
     "craft-cli>=2.3.0",
     "craft-grammar>=2.0.0",
     "craft-parts>=2.2.1",
-    "craft-providers>=2.0.0",
+    "craft-providers>=2.1.0",
     "craft-platforms~=0.5",
     "craft-providers>=2.0.0",
     "craft-store>=3.1.0",