Update tests use runtime jar from maven for spark submission to cover Databricks

feathr_project/test/test_user_workspace/feathr_config_maven.yaml

@@ -68,7 +68,7 @@ offline_store:
 spark_config:
   # choice for spark runtime. Currently support: azure_synapse, databricks
   # The `databricks` configs will be ignored if `azure_synapse` is set and vice versa.
-  spark_cluster: 'azure_synapse'
+  spark_cluster: 'databricks'
   # configure number of parts for the spark output for feature generation job
   spark_result_output_parts: '1'
 
@@ -107,13 +107,5 @@ online_store:
     ssl_enabled: True
 
 feature_registry:
-  purview:
-    # Registry configs
-    # register type system in purview during feathr client initialization. This is only required to be executed once.
-    type_system_initialization: true
-    # configure the name of the purview endpoint
-    purview_name: 'feathrazuretest3-purview1'
-    # delimiter indicates that how the project/workspace name, feature names etc. are delimited. By default it will be '__'
-    # this is for global reference (mainly for feature sharing). For example, when we setup a project called foo, and we have an anchor called 'taxi_driver' and the feature name is called 'f_daily_trips'
-    # the feature will have a globally unique name called 'foo__taxi_driver__f_daily_trips'
-    delimiter: '__'
+  # The API endpoint of the registry service
+  api_endpoint: "https://feathr-sql-registry.azurewebsites.net/api/v1"