New version: PromptingTools v0.59.0

[JuliaRegistrator]

• Registering package: PromptingTools
• Repository: https://github.com/svilupp/PromptingTools.jl
• Created by: @svilupp
• Version: v0.59.0
• Commit: 06fcd59d75100d0a9ed7d8e8281bea84a4836bde
• Reviewed by: @svilupp
• Reference: svilupp/PromptingTools.jl@06fcd59#commitcomment-148140175
• Description: Streamline your life using PromptingTools.jl, the Julia package that simplifies interacting with large language models.
• Release notes:

### Breaking Changes
- New field `name` introduced in `AbstractChatMessage` and `AIToolRequest` messages to enable role-based workflows. It initializes to `nothing`, so it is backward compatible.

### Added
- Extends support for structured extraction with multiple "tools" definitions (see `?aiextract`).
- Added new primitives `Tool` (to re-use tool definitions) and a function `aitools` to support mixed structured and non-structured workflows, eg, agentic workflows (see `?aitools`).
- Added a field `name` to `AbstractChatMessage` and `AIToolRequest` messages to enable role-based workflows.
- Added a support for partial argument execution with `execute_tool` function (provide your own context to override the arg values).
- Added support for [SambaNova](https://sambanova.ai/) hosted models (set your ENV `SAMBANOVA_API_KEY`). 
- Added many new models from Mistral, Groq, Sambanova, OpenAI.

### Updated
- Renamed `function_call_signature` to `tool_call_signature` to better reflect that it's used for tools, but kept a link to the old name for back-compatibility.
- Improves structured extraction for Anthropic models (now you can use `tool_choice` keyword argument to specify which tool to use or re-use your parsed tools).
- When log probs are requested, we will now also log the raw information in `AIMessage.extras[:log_prob]` field (previously we logged only the full sum). This enables more nuanced log-probability calculations for individual tokens.

### Commits

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines are all met! ✅

Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round.

2. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.