text: Title: [FR] Update Anthropic tracing to handle thinking blocks for claude-3.7-sonnet
  Body: ### Willingness to contribute
  
  Yes. I can contribute this feature independently.
  
  ### Proposal Summary
  
  The current MLflow integration for Anthropic doesn't properly handle the new "thinking" feature in Claude Sonnet. When thinking is enabled, Claude returns content with specialized ThinkingBlock and TextBlock objects, but these aren't correctly processed in the message conversion function. As a result, the chat messages aren't properly captured during MLflow tracing, leading to incomplete traces (missing "chat" tab).
  
  <img width="880" alt="Image" src="https://github.com/user-attachments/assets/a203b644-6f7d-403f-8023-365a145b7a50" />
  
  I propose updating the implementation to check for the `thinking` block type and filter it out in the `convert_message_to_mlflow_chat` function, which restores the chat tab. The thinking contents are still captured in the inputs/outputs tab.
  
  A more comprehensive handling of this issue would involve adding a `thinking` type to the chat section and would likely involve updates to multiple providers that now support thinking.
  
  ### Motivation
  
  > #### What is the use case for this feature?
  
  Working with the new `claude-3-7-sonnet-20250219` model with thinking enabled.
  
  > #### Why is this use case valuable to support for MLflow users in general?
  
  `claude-3-7-sonnet-20250219` is the latest and most capable claude model and will likely see substantial usage.
  
  > #### Why is this use case valuable to support for your project(s) or organization?
  
  this will address a limitation in the tracing handling of `claude-3-7-sonnet-20250219`
  
  > #### Why is it currently difficult to achieve this use case?
  
  (see above)
  
  ### Details
  
  Proposed simple fix here:
  
  https://github.com/mlflow/mlflow/blob/9cf17478518f632004ae062e87224fea0f704b45/mlflow/anthropic/chat.py#L50
  
  
  ```python
          for content_block in content:
              # Skip ThinkingBlock objects
              if hasattr(content_block, "type") and getattr(content_block, "type") == "thinking":
                  continue
                  
              # Handle TextBlock objects directly
              if hasattr(content_block, "type") and getattr(content_block, "type") == "text":
                  if hasattr(content_block, "text"):
                      contents.append(TextContentPart(text=getattr(content_block, "text"), type="text"))
                  continue
  ```
  
  ### What component(s) does this bug affect?
  
  - [ ] `area/artifacts`: Artifact stores and artifact logging
  - [ ] `area/build`: Build and test infrastructure for MLflow
  - [ ] `area/deployments`: MLflow Deployments client APIs, server, and third-party Deployments integrations
  - [ ] `area/docs`: MLflow documentation pages
  - [ ] `area/examples`: Example code
  - [ ] `area/model-registry`: Model Registry service, APIs, and the fluent client calls for Model Registry
  - [x] `area/models`: MLmodel format, model serialization/deserialization, flavors
  - [ ] `area/recipes`: Recipes, Recipe APIs, Recipe configs, Recipe Templates
  - [ ] `area/projects`: MLproject format, project running backends
  - [ ] `area/scoring`: MLflow Model server, model deployment tools, Spark UDFs
  - [ ] `area/server-infra`: MLflow Tracking server backend
  - [ ] `area/tracking`: Tracking Service, tracking client APIs, autologging
  
  ### What interface(s) does this bug affect?
  
  - [ ] `area/uiux`: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  - [ ] `area/docker`: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
  - [ ] `area/sqlalchemy`: Use of SQLAlchemy in the Tracking Service or Model Registry
  - [ ] `area/windows`: Windows support
  
  ### What language(s) does this bug affect?
  
  - [ ] `language/r`: R APIs and clients
  - [ ] `language/java`: Java APIs and clients
  - [ ] `language/new`: Proposals for new client languages
  
  ### What integration(s) does this bug affect?
  
  - [ ] `integrations/azure`: Azure and Azure ML integrations
  - [ ] `integrations/sagemaker`: SageMaker integrations
  - [ ] `integrations/databricks`: Databricks integrations