refactor: passing down ssl verification as it's available in DDGS class

[FaresKi]

Description

Please include:

• Summary of changes: DDGS provides SSL verification option (with verification enabled by default). Adding it to the DuckDuckGo tool also.
• Related issues: N/A
• Motivation and context: Experimenting with the introduction example, and ran into SSL issues (cough cough enterprise stuff cough cough)
• Environment or dependencies: No changes.
• Impact on AI/ML components: (If applicable) N/A

Fixes # N/A

Type of change

Please check the options that are relevant:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Model update
• Infrastructure change

Checklist

• My code follows Phidata's style guidelines and best practices
• I have performed a self-review of my code
• I have added docstrings and comments for complex logic
• My changes generate no new warnings or errors
• I have added cookbook examples for my new addition (if needed)
• I have updated requirements.txt/pyproject.toml (if needed)
• I have verified my changes in a clean environment

Additional Notes

Include any deployment notes, performance implications, or other relevant information: When trying to format, according to the CONTRIBUTING.md, the ruff module wasn't installed by default using the create venv script. I can see it's in the dev modules inside the pyproject.toml. Is that expected? Thanks!

[manthanguptaa]

A better param would be verify_ssl. What do you think?

[FaresKi]

Makes sense. Will change.

[FaresKi]

Done