Args conflict with serverless offline

I want to run serverless offline on a port that is not the default. Currently if I run

sls offline

everything is brought up correctly. However if I run

sls offline --port 3541

with the aim of launching the serverless offline API I have written on port 3541, DynamoDB will pick the port arg up as its own and launch on port 3541 instead. It would be great if this conflict could be resolved. I don't know how serverless-dynamodb-local works extremely well, but it would be good if it didn't pick up args when run via sls offline (i.e. all config is picked up only from serverless.yml instead in this case), or if the args could be named in such a way that they do not collide with those for sls offline.

Start by tracing how the plugin handles arguments when invoked through `sls offline`, focusing on the `--port` conflict described in the issue. Confirm the behavior with `sls offline` and `sls offline --port 3541`; done means the offline API uses port 3541 without DynamoDB Local incorrectly adopting that port.

Written by the indexing model from the issue text.