Kokoro performance job uploads to same BQ table as Jenkins

tools/internal_ci/linux/grpc_full_performance_master.sh

@@ -26,7 +26,7 @@ tools/run_tests/run_performance_tests.py \
     --category scalable \
     --remote_worker_host grpc-kokoro-performance-server-8core grpc-kokoro-performance-client-8core grpc-kokoro-performance-client2-8core \
     -u kbuilder \
-    --bq_result_table performance_test.kokoro_performance_experiment \
+    --bq_result_table performance_test.performance_experiment \
     --xml_report reports/8core/sponge_log.xml \
     || EXIT_CODE=1
 
@@ -40,7 +40,7 @@ tools/run_tests/run_performance_tests.py \
     --category scalable \
     --remote_worker_host grpc-kokoro-performance-server-32core grpc-kokoro-performance-client-32core grpc-kokoro-performance-client2-32core \
     -u kbuilder \
-    --bq_result_table performance_test.kokoro_performance_experiment_32core \
+    --bq_result_table performance_test.performance_experiment_32core \
     --xml_report reports/32core/sponge_log.xml \
     || EXIT_CODE=1
 
@@ -52,7 +52,7 @@ tools/run_tests/run_performance_tests.py \
     -l csharp \
     --category scalable \
     --remote_worker_host grpc-kokoro-performance-windows1 grpc-kokoro-performance-windows2 \
-    --bq_result_table performance_test.kokoro_performance_experiment_windows \
+    --bq_result_table performance_test.performance_experiment_windows \
     --xml_report reports/windows/sponge_log.xml \
     || EXIT_CODE=1