Private Datasets: GQL: make new parameters mandatory, after frontend update

[s373r]

An optional argument for creating datasets via GQL has been added for now:

• Via Private Datasets: Update use case: Creating a dataset #761

---

Once kamu-web has done the migration and the changes have been pushed to the deployed environments, make the added argument mandatory:

type DatasetsMut {
	...

	Creates a new empty dataset
	"""
	createEmpty(
		datasetKind: DatasetKind!,
		datasetAlias: DatasetAlias!, 
-		datasetPubliclyAvailable: Boolean
+		datasetPubliclyAvailable: Boolean!
	): CreateDatasetResult!

	"""
	Creates a new dataset from provided DatasetSnapshot manifest
	"""
	createFromSnapshot(
		snapshot: String!,
		snapshotFormat: MetadataManifestFormat!
-		datasetPubliclyAvailable: Boolean
+		datasetPubliclyAvailable: Boolean!
	): CreateDatasetFromSnapshotResult!

	...
}

A task to update the frontend:

• Private Datasets, "Create a new dataset" page: Unlock dataset visibility selection kamu-web-ui#411