Removed false path as timing violations are not reported by timequest

but hardware behaviour seems to have a timing violation

applications/ta2/libraries/ta2_unb2b_bsp/hardware/unb2b/top_post.sdc

@@ -77,6 +77,6 @@ set_multicycle_path -to * -hold 3 -from {freeze_wrapper_inst|board_kernel_reset_
 
 # Cut path to twoXclock_consumer (this instance is only there to keep 
 # kernel interface consistent and prevents kernel_clk2x to be swept away by synthesis)
-set_false_path -from * -to freeze_wrapper_inst|pr_region_inst|*|twoXclock_consumer_NO_SHIFT_REG
+#set_false_path -from * -to freeze_wrapper_inst|pr_region_inst|*|twoXclock_consumer_NO_SHIFT_REG