Update skip_remote_state_provision default value

[viniciusdc]

Fixes | Closes | Resolves #

Please remove anything marked as optional that you don't need to fill in.
Choose one of the keywords preceding to refer to the issue this PR solves, followed by the issue number (e.g Fixes # 666).
If there is no issue, remove the line. Remove this note after reading.

Changes introduced in this PR:

• Update skip_remote_state_provision default value from True to False

By keeping the skip_remote_state_provision default value as True, we were inadvertently revoking the creation of the terraform state bucket during the first deployments. Which is used during the stage provision phase:

nebari/nebari/deploy.py

Lines 201 to 208 in 77d15e7

	if (
	config["provider"] not in {"existing", "local"}
	and config["terraform_state"]["type"] == "remote"
	):
	if skip_remote_state_provision:
	print("Skipping remote state provision")
	else:
	provision_01_terraform_state(stage_outputs, config)

I think the reason we didn't spot this sooner as due to until #1519 we still used a mix of the new CLI with the old qhub entry points.

Image of the error caused during deployment on GCP with terraform_state: remote (default) set in the config

nebari deploy -c nebari-config.yaml --dns-provider cloudflare --dns-auto-provision --disable-prompt

Even with no mention of --skip-remote-state-provision you can see the log message right at the beginning finalizing the skip.

Types of changes

What types of changes does your PR introduce?

Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

Requires testing

• Yes
• No

In case you checked yes, did you write tests?

• Yes
• No

Documentation

Does your contribution include breaking changes or deprecations?
If so have you updated the documentation?

• Yes, docstrings
• Yes, main documentation
• Yes, deprecation notices

Further comments (optional)

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered and more.

[viniciusdc]

There seems to be a problem with pytest running the jupyterhub ssh test. I will handle that in another PR. I ran IT with this branch all working.