Bug - Fix issues caused by omegaconf version update

[RyoYang]

Description

• Fix executor for Benchmark Execution Without Explicit Framework Field
• Fix mca misspell issue
• Timeout should be None if it is not explicated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.78%. Comparing base (7af75df) to head (3039a9f).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #636   +/-   ##
=======================================
  Coverage   85.78%   85.78%           
=======================================
  Files          97       97           
  Lines        6923     6923           
=======================================
  Hits         5939     5939           
  Misses        984      984           

Flag	Coverage Δ
cpu-python3.6-unit-test	71.61% <100.00%> (ø)
cpu-python3.7-unit-test	71.61% <100.00%> (ø)
cpu-python3.8-unit-test	71.64% <100.00%> (ø)
cuda-unit-test	83.87% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[RyoYang]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[guoshzhao]

Could you please check if:

1. All configs used in Prod env have timeout set? https://msazure.visualstudio.com/One/_git/SuperBench?path=/config
2. Are these two bugs related with omegaconf version update?
   If the answers are Yes, I am ok with this PR.

If the answer is No for 1, then we changed the behavior of Prod.
If the answer is No for 2, maybe we need to split to two PRs?

Thanks Yang for the efforts.

[RyoYang]

Could you please check if:

1. All configs used in Prod env have timeout set? https://msazure.visualstudio.com/One/_git/SuperBench?path=/config
2. Are these two bugs related with omegaconf version update?
   If the answers are Yes, I am ok with this PR.

If the answer is No for 1, then we changed the behavior of Prod. If the answer is No for 2, maybe we need to split to two PRs?

Thanks Yang for the efforts.

1. The change addresses a bug in the previous PR where all benchmarks without a specified timeout were forcefully set to a 60-second timeout. For the production configuration, if the timeout is not set, it should default to None, meaning the benchmark should have no timeout.
2. Yes, these changes are related to the update of the omegaconf version.
   Thanks a lot for the review.