Default schemes is based on order in the spec instead of the current context

Expected Behavior

If a spec is having http and https in the schemes section, swagger-ui should default to the one that it was loaded on. For example, in dev over http, it should have http selected in the dropdown by default and do http request by default. In prod over https, it should have https selected in the dropdown by default and do https request by default.

This seems related to this bug: https://github.com/swagger-api/swagger-ui/issues/1382

Current Behavior

The default selected scheme and the one that is used for the query is always the first one in the list in the spec

Possible Solution

I didn't check the code at all, I'm not very good in javascript. But this related bug seems to had a solution: https://github.com/swagger-api/swagger-ui/issues/1382

Context

Different environment use the same spec. The order in which we declare the possible schemes should not decide which one is used by default.

No files or tests are named. Reproduce the issue in Swagger UI with a Swagger 2.0 spec listing both http and https schemes, then trace the default dropdown selection and request behavior. Done means the current page protocol is selected and used by default instead of the first scheme in the spec.