Added Telegram domains to Shared Credentials

[gracjankn]

Overall Checklist

• I agree to the project's Developer Certificate of Origin
• The top-level JSON objects are sorted alphabetically
• There are no open pull requests for the same update

for shared-credentials.json

• There's evidence the domains are currently related (SSL certificates, DNS entries, valid links between sites, legal documents etc.)
• If using shared, the new group serves login pages on each of the included domains, and those login pages accept accounts from the others. (For example, we wouldn't use a shared association from google.co.il to google.com, because google.co.il redirects to accounts.google.com for sign in.)
• If using from and to, the new group, the from domain(s) redirect to the to domain to log in.

Telegram.me is used to autofill credentials in Telegram for iOS. Telegram.org is used for the web app (https://web.telegram.org).

[rmondello]

From what I can tell, telegram.me redirects to telegram.org, so a “from” / “to” relationship would be more correct here.

[gracjankn]

It does redirect when opened in the browser, however Password Autofill on iOS suggests an account for login to the Telegram app only if "telegram.me" is also added to the domains in the Passwords app.

Would "from" and "to" relationship work in this case?

[rmondello]

On iOS, we will interpret this correctly and do exactly what you want. :)

[gracjankn]

I changed the relationship type in the new commit. Does that look right?