Overrides default value for dask-labextension

[viniciusdc]

Fixes | Closes | Resolves #1326

Changes introduced in this PR:

• Updates the default value of browserDashboardCheck from False to True
  This will guarantee that every spawned profile has the fix for the dask-gateway and dask-labextension dashboard issue.

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
• Maintance related task.

Testing

Requires testing

• Yes
• No

In case you checked yes, did you write tests?

• Yes
• No

Further comments (optional)

This is a very simple addition to address the remaining needs of #1012

[viniciusdc]

This is not blocked by #1321 but it's recommended to have that one merged first.

[iameskild]

This looks good to me!
My only question is how are these overrides handled? I don't see this json referenced anywhere else.

[viniciusdc]

This looks good to me! My only question is how are these overrides handled? I don't see this json referenced anywhere else.

For this case specifically (an extension) Jupyterlab has a mechanism to override extension settings using an overrides.json file, which is a little bit different than the usual override options available for the user in our configuration.
In other words, we shouldn't expect the user to change this.

[viniciusdc]

This was tested already with a GCP deployment.

[iameskild]

Beautiful! Thanks a lot @viniciusdc :)