Do not store master protocol in init to better support mixed SSL domains

I noticed on s.d.o that some users have a different display on their user account page, most of them had the link to their Profile on http://drupal.org/ and some others didn't. It turns out this was due to some accounts having a http init and some others using https. Here is the conversation I had with coltrane and greggles.

greggles:

Seems like a bug and one we're likely to hit more as we roll out more and more https. I'm not sure at the moment what the *right* behavior is though as d.o migrates to https we'll have inits with both styles. I think the init probably should not contain the protocol and should instead use whatever the site is "set" to use.

coltrane:

My recommendation for Bakery on any SSL-enabled site is to put all authenticated users over SSL for this reason.

The good thing is that it does not seem to prevent logging in into s.d.o, and it seems to fix itself too!. Here is what I did as an experiment from an initial situation where my init was http:
- set my init to https on slave => am still logged in slave
- logout of master => got logged out of slave
- reset password on master and log in on master => got logged in on slave, init on slave is still https
- loaded my user page on slave => init got fixed to http

I confirmed that setting the init manually from https to http fixes the issue on the profile page.