Change session option values if they don't work with EPs being registered for the session

[hariharans29]

Description:

• Some session option values (default or user provided) may not work with some EPs. Rather than put the onus on the user to know these, make the appropriate choice for the session option while logging the change.
  • If the issue is with user provided options, it is fair to throw, but in cases where the default session option value (not user provided) does not work with some EPs, it doesn't seem fair to throw and have the user change it to the non-default working value. So picking the approach of changing the faulty session option value - default or user provided.

Motivation and Context
Takeaway from #4630

[pranavsharma]

The C API returns an error for this kind of scenario. https://github.com/microsoft/onnxruntime/blob/master/onnxruntime/core/session/onnxruntime_c_api.cc#L384 . As discussed, let's be consistent - either swallow the error or return an error.

[hariharans29]

The C API returns an error for this kind of scenario. https://github.com/microsoft/onnxruntime/blob/master/onnxruntime/core/session/onnxruntime_c_api.cc#L384 . As discussed, let's be consistent - either swallow the error or return an error.

Removed the duplicate handling logic in the C API layer (was superfluous to begin with given that eventually RegisterExecutionProvider() did the exact same thing and there is a call to RegisterExecutionProvider()). With this all handling is done in a centralized place and keeps all APIs consistent.