This PRfixes#15035, I have tested it on my instance and it works as expected.

I have opted to default to null, that way we don't have to hardcode our own default and we let the Docker provider default to whatever it wants.
This has the downside that it makes the template a little less readable, but it has the upside that we don't have to update the default if for some reason it ever changes.

We could also do something like this, but I like it less.

variable"docker_socket" {default="unix:///var/run/docker.sock"description="Docker socket URI"type=string}provider"docker" {host=var.docker_socket}

I have not edited the templates that are not present in examples/templates (namelyexamples/jfrog/docker andexamples/parameters), should I also edit these as well?
Maybe we would also want to move them to examples/templates in a separate PR?

NOTE: this PR does not cover using authenticated sources, so it's likely that only unix and tcp sockets would work out of the box but I think we don't want to include authenticated sockets OOTB (e.g SSH) because that would overcomplicate the template.

cc:@matifali