BUG: NatsJS subscribe rewrites original ConsumerConfig(filter_sibject=...) option

[Lancetnik]

What version were you using?

nats-py==2.4.0

What environment was the server running in?

nats:latest

Is this defect reproducible?

import asyncio
import nats
from nats.js.api import ConsumerConfig


async def main():
    nc = await nats.connect()
    js = nc.jetstream()
    await js.add_stream(name="test-stream", subjects=["in_subject"])
    await js.subscribe("in_subject", config=ConsumerConfig(
        filter_subject="in_"
    ))


if __name__ == '__main__':
    asyncio.run(main())

Given the capability you are leveraging, describe your expectation?

NatsJS respects the original ConsumerConfig

Given the expectation, what is the defect you are observing?

At the first subscriber creation, nats-py ignores the original config and forcely rewrites some options (filter_subject is a founded example)

https://github.com/nats-io/nats.py/blob/main/nats/js/client.py#L281