[Feature Request]: Add Creduent zero-trust agent identity verification tool

[cyberfascinate]

Feature Area

Integration with external tools

Is your feature request related to a an existing bug? Please link it here.

NA

Describe the solution you'd like

Add native support for Creduent agent identity verification to CrewAI (crewai).

As autonomous agents delegate tasks to sub-agents and external tools in CrewAI agent loops, zero-trust verification of target agent identity is critical to prevent untrusted execution loops and unverified prompt injections.

Creduent (creduent) is an open-source agent identification protocol that performs local cryptographic signature verification (Ed25519 + JCS RFC 8785) of agent URIs (agent://<namespace>/<name>) in under 5ms.

Introduce CreduentVerificationTool to wrap and verify target agent attestations prior to task delegation:

from creduent.integrations.crewai import CreduentVerificationTool

tool = CreduentVerificationTool(
    agent_uri="agent://researcher.dev/agent",
    timeout=10
)

### Describe alternatives you've considered

```markdown
Alternative approaches considered:
1. Custom HTTP verification wrappers around CrewAI tools.
2. Manual API calls before task execution.
These don't work ideally because out-of-band network calls add latency to the execution loop and lack standard schema validation across frameworks.

### Additional context

- Python SDK: `pip install creduent` / `pip install crewai`
- Open-Source Protocol & Specifications: https://github.com/idevsec/creduent
I have the implementation and unit test suite ready to submit as a Pull Request.

### Willingness to Contribute

Yes, I'd be happy to submit a pull request

[Mahnoor-Zaffar]

One-Line Fix:
Implement the CreduentVerificationTool to enable zero-trust identity verification for agents in CrewAI.
Hey, I can implement that?

[cyberfascinate]

Hi @Mahnoor-Zaffar , thanks for stepping in!

Since we already have the CreduentVerificationTool implementation and unit test suite ready in our repo, I will be opening the Pull Request for this directly to link to this issue.

Appreciate your support!