Remove comment from metaschema that some fields are not implemented

It seems those fields are actually in use.

Author: badboy

Diff for: schemas/metadata/metaschema/metaschema.1.schema.json

@@ -12,7 +12,7 @@
           "type": "string"
         },
         "bq_dataset_family": {
-          "description": "NOT YET IMPLEMENTED: The base name for the destination BigQuery dataset; if this is set to 'telemetry', the pipeline will write into 'telemetry_live'",
+          "description": "The base name for the destination BigQuery dataset; if this is set to 'telemetry', the pipeline will write into 'telemetry_live'",
           "type": "string"
         },
         "bq_metadata_format": {
@@ -25,7 +25,7 @@
           "type": "string"
         },
         "bq_table": {
-          "description": "NOT YET IMPLEMENTED: The name of the destination BigQuery table",
+          "description": "The name of the destination BigQuery table",
           "type": "string"
         },
         "expiration_policy": {

Diff for: templates/metadata/metaschema/metaschema.1.schema.json

@@ -15,11 +15,11 @@
         },
         "bq_table": {
           "type": "string",
-          "description": "NOT YET IMPLEMENTED: The name of the destination BigQuery table"
+          "description": "The name of the destination BigQuery table"
         },
         "bq_dataset_family": {
           "type": "string",
-          "description": "NOT YET IMPLEMENTED: The base name for the destination BigQuery dataset; if this is set to 'telemetry', the pipeline will write into 'telemetry_live'"
+          "description": "The base name for the destination BigQuery dataset; if this is set to 'telemetry', the pipeline will write into 'telemetry_live'"
         },
         "bq_metadata_format": {
           "type": "string",