Getting deprecated messages when using RabbitMQ

[xlight05]

Description:
$Subject. Getting the following error when we use a rabbitmq service.

 wso2@anjanas  ~/ballerina-playground/iit_session/github_liker  bal run
Compiling source
        wso2/github_liker:0.1.0
ballerinax/rabbitmq:2.10.0 [central.ballerina.io ->/Users/wso2/.ballerina/repositories/central.ballerina.io/bala/ballerinax/rabbitmq/2.10.0]  100% [==========] 769/769
        ballerinax/rabbitmq:2.10.0 pulled from central successfully
WARNING [ballerinax/rabbitmq/2.10.0::client.bal:(165:39,165:46)] usage of construct 'ballerinax/rabbitmq:2.10.0:Message' is deprecated
WARNING [ballerinax/rabbitmq/2.10.0::client.bal:(180:40,180:47)] usage of construct 'ballerinax/rabbitmq:2.10.0:Message' is deprecated
WARNING [ballerinax/rabbitmq/2.10.0::message.bal:(25:1,31:4)] constructs annotated as '@deprecated' must have 'Deprecated' documentation

Steps to reproduce:

Affected Versions:
U8

OS, DB, other environment details and versions:

Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

[aashikam]

This is expected behaviour, the usages of this deprecated Message record will be removed in the next release.

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.

[aashikam]

#5093 duplicate issue

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.