Bug: TestRabbitBroker does not throw error when rpc and reply_to are both provided

[maxalbert]

Describe the bug

When using the TestRabbitBroker with the argument with_real=False, the command broker.publish() will allow the simultaneous use of the arguments rpc and reply_to, even though this should trigger a SetupError.

How to reproduce

Save the following script as example.py, then run

$ pytest example.py

import pytest
from faststream import FastStream
from faststream.rabbit import RabbitBroker, TestRabbitBroker

broker = RabbitBroker("amqp://guest:guest@localhost:5672/")
app = FastStream(broker)

@broker.subscriber("in-queue")
async def handle_msg(msg: str) -> str:
    return f"Received message: {msg!r}"

@pytest.mark.asyncio
async def test_rpc():
    async with TestRabbitBroker(broker, with_real=False) as br:
        response = await br.publish(
            "Hello there!",
            "in-queue",
            rpc=True,
            reply_to="reponse-queue",
        )
        assert response == "Received message: 'Hello there!'"

Expected behavior

I expect FastStream to throw an exception (which it does when using with_real=True):

faststream.exceptions.SetupError: You should use `reply_to` to send response to
                                  long-living queue and `rpc` to get response in sync mode.

Observed behavior
There is no error and the test passes even though it should fail.

Environment

$ faststream -v
Running FastStream 0.5.3 with CPython 3.12.3 on Darwin