[Router] Fixed the Logging Issues and Reverted the Changes for RCV Tests

Fixed the output of the SSSP time of the connection router, which caused
VTR flow log parser issues and made CI mad.

Reverted the changes for RCV tests, which are not working and appear to
be too simple to be useful. It needs more time and effort to make a
comprehensive set of regression tests for the RCV technique. We tend to
postpone this task since it is not the main purpose of this PR.

Author: ueqri

vpr/src/route/connection_router.h

@@ -51,7 +51,7 @@ class ConnectionRouter : public ConnectionRouterInterface {
     }
 
     ~ConnectionRouter() {
-        VTR_LOG("Serial Connection Router is being destroyed. Time spent computing SSSP: %.3f seconds\n.", this->sssp_total_time.count() / 1000000.0);
+        VTR_LOG("Serial Connection Router is being destroyed. Time spent computing SSSP: %.3f seconds.\n", this->sssp_total_time.count() / 1000000.0);
     }
 
     // Clear's the modified list.  Should be called after reset_path_costs

vtr_flow/tasks/regression_tests/vtr_reg_strong/strong_yoyo_budgets/config/config.txt

@@ -87,4 +87,3 @@ regression_tests/vtr_reg_strong/strong_timing_no_fail
 regression_tests/vtr_reg_strong/strong_noc
 regression_tests/vtr_reg_strong/strong_flat_router
 regression_tests/vtr_reg_strong/strong_routing_constraints
-regression_tests/vtr_reg_strong/strong_yoyo_budgets

vtr_flow/tasks/regression_tests/vtr_reg_strong/task_list.txt

@@ -82,4 +82,3 @@ regression_tests/vtr_reg_strong_odin/koios_test
 regression_tests/vtr_reg_strong_odin/koios_test_no_hb
 regression_tests/vtr_reg_strong_odin/strong_timing_fail
 regression_tests/vtr_reg_strong_odin/strong_timing_no_fail
-regression_tests/vtr_reg_strong_odin/strong_yoyo_budgets