Allow the option visibilityTimeout to be configured after initialisation

[nicholasgriffintn]

Problem

As suggested in the discussion here:

#369

It would be good to allow users to configure the option visibilityTimeout after the consumer has started, this will allow users to change the timeout depending on external factors, such as the runtime configuration.

Solution

A new method should be added (possibly something along the lines of changeVisibilityTimeout that will allow the user to provide a new timeout.

The method should verify the provided timeout and then change the option.

It would be good to add a new emitter as well for option changed, users can then listen to this.

We are open to PRs for this change :)

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.