Stop propagating 'id' field from Message object to request payload

[B-Step62]

Resolving #6

The new ChatDatabricks implementation propagates the id fields from the input Message objects to the underlying model endpoint. It causes an error because not all endpoints support id field in the input payload e.g. our FMAPIs.

Indeed, the input messages often do not have id fields if it is specified by users. However, when we pass the chat history to the ChatDatabricks class, it contains AIMessage objects from the previous response, which often contain id field.

Indeed, this is regressoin fromthe old community ChatDatabricks, which does not propagate id field. Therefore, this PR simply revert the new class to original behavior.

Testing

• Unit test
• Validated with the sample code user provided in the issue ^

[BenWilson2]

LGTM. We should raise this with the serving team to see if an optional id field can be added to those endpoints. application interfaces with these endpoints can probably benefit from the propagation of this metadata.