Change QoR parsing configs to use the fixed channel width variant

[AmirhosseinPoolad]

Changes the parse_file attribute of tests that use fixed channel widths instead of doing the minimum channel width search to use vpr_fixed_chan_width.txt instead of vpr_standard.txt

[AmirhosseinPoolad]

Since the parse_results.txt for some of the tests are going to be different, I need to update golden results for those tests. Here's a checklist to make sure I don't forget anything.

• vtr_reg_strong
• vtr_reg_strong_odin
• vtr_reg_nightly_test1 (Did not actually regenerated anything. Only changed task was symbiflow but the test does not work and isn't in the tasklist)
• vtr_reg_nightly_test1_odin (Same as above)
• vtr_reg_nightly_test2
• vtr_reg_nightly_test2_odin
• vtr_reg_nightly_test4
• vtr_reg_nightly_test4_odin
• vtr_reg_nightly_test5
• vtr_reg_nightly_test6
• vtr_reg_valgrind (No pass requirements)
• vtr_reg_weekly

[AmirhosseinPoolad]

Sorry to hijack the PR but since this is going to require regenerating a ton of golden results I made NightlyTestManual generate and upload them. I can remove the commit if you disagree. @AlexandreSinger FYI.

[AlexandreSinger]

No worries @AmirhosseinPoolad , no one appears to be using it! Do please also update the golden results for some of the failing nightly tests while you are at it! 2 small ones were failing before! If not do not worry about it!

[vaughnbetz]

LGTM. I know you tell me some nightly tests results are broken before this change, but they are small ones where the QoR is just a bit out of date. Just go ahead and do a global golden results update for this change, as long as you're confident there are no real issues in the current QoR failures.