fix: Allow non blocking all the way down to the instance level

[bougyman]

• fix: Allows non-blocking setup_worker method
• fix: Ensure we do not block in non-blocking mode

This allows running specs and any other tasks
that you want to accomplish without being blocked
by worker threads sleeping

[Copilot]

Pull Request Overview

This PR fixes blocking behavior in the NATS API server to allow non-blocking operation at the instance level. The changes enable running specs and other tasks without being blocked by worker threads sleeping.

• Adds a blocking parameter throughout the worker spawn chain to control blocking behavior
• Splits worker setup into blocking (setup_worker!) and non-blocking (setup_worker) variants
• Refactors parameter passing to use keyword arguments for better clarity

[Copilot]

The conditional logic is inverted. When blocking is true, the method calls setup_worker! which blocks with sleep, but then immediately returns, preventing the sleep from executing. This should be unless blocking or the logic should be restructured.

Suggested change

	return worker.setup_worker!(nats_url: url, service_opts: opts) if blocking
	worker.setup_worker(nats_url: url, service_opts: opts)
	if blocking
	worker.setup_worker!(nats_url: url, service_opts: opts)
	else
	worker.setup_worker(nats_url: url, service_opts: opts)
	end

[BryceARich]

I think it got this wrong. Not sure why it thinks the sleep is prevented from executing

[Copilot]

The build_service_opts method call uses named parameter syntax but the method definition shows service_opts: parameter. This should be build_service_opts(service_opts: service_opts) for clarity.

Suggested change

	@service = @client.services.add(build_service_opts(service_opts:))
	@service = @client.services.add(build_service_opts(service_opts: service_opts))