Resolve remaining TLS issues with S3-redirected domain aliases

[nastevens]

With the reorg per rust-embedded/wg#208, all docs are now hosted under https://docs.rust-embedded.org, and TLS certs are lined up correctly for that. However, the following will still fail if you try to go directly to the https version - this is because the following pages actually host a HTTP redirect and there are certificate issues going from AWS to Github:

• https://www.areweembeddedyet.com
• https://www.rust-embedded.com
• https://areweembeddedyet.com
• https://rust-embedded.com

I think at this point the right way to fix this will be to get TLS certs for those specific domains (probably through LetsEncrypt) and then run a lambda at those endpoints to do the HTTP redirect.

[nastevens]

Something like this with certs issued for the areweembeddedyet.com and rust-embedded.com domains should work: https://simonecarletti.com/blog/2016/08/redirect-domain-https-amazon-cloudfront/