chore: update third-party notices for boto3 1.43.80

[kevinmessiaen]

Description

The giskard-core stable Release run failed at make check / check-notices: generated notices listed boto3/botocore 1.43.80 while THIRD_PARTY_NOTICES.md still had 1.43.78.

This PR regenerates notices with make generate-notices so Release can be re-run on main.

No package versions or lockfile changes.

Related Issue

Unblocks the stable lib release cascade (core 1.0.1 first).

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Coding agents

Autonomous agents with no human in the loop must read AUTONOMOUS.md before opening a PR.

PR title: agent-opened PRs must end the title with 🤖🤖🤖🤖 (exactly four robot emojis). Do not omit — that suffix is how the expedited agent PR workflow picks up the PR.

Checklist

• I've read the CODE_OF_CONDUCT.md document.
• I've read the CONTRIBUTING.md guide.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in NumPy format for all the methods and classes that I created or modified.
• I've updated the uv.lock running uv lock (only applicable when pyproject.toml has been
  modified)

After this merges, re-dispatch Release on main: package=giskard-core, bump_type=none, release_type=stable, dry_run=false.