Add First-Party Set Information for Yandex domains

[IvanKharpalev]

No description provided.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[EnsDeLiz]

#20

[sjledoux]

Hello, there have been some recent changes that affect your PR. In particular, the checks now look for the well-known to be hosted at <domain.tld>/.well-known/related-website-set.json, so please change your well-known files to match this endpoint.

As an additional suggestion, it appears that your many members of your associatedSites list are ccTLD variants of each other. The ccTLDs field of the set exists for this reason, so please feel free to use it for your ccTLD aliases. RSA is only granted for the first five members of the associatedSites list, so placing your variants in the ccTLD may be beneficial to your set submission.

[Creatormrh]

Add first party

[github-actions]

It appears you have failed some tests. Here are your results:
Experienced an error when trying to access https://ya.ru/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://adfox.net/.well-known/related-website-set.json; error was: <urlopen error [Errno -5] No address associated with hostname>
Experienced an error when trying to access https://adfox.ru/.well-known/related-website-set.json; error was: Expecting value: line 1 column 1 (char 0)
Experienced an error when trying to access https://auto.ru/.well-known/related-website-set.json; error was: Expecting value: line 1 column 1 (char 0)
Experienced an error when trying to access https://clck.ru/.well-known/related-website-set.json; error was: Expecting value: line 1 column 1 (char 0)
Experienced an error when trying to access https://clients.site/.well-known/related-website-set.json; error was: <urlopen error [Errno -5] No address associated with hostname>
Experienced an error when trying to access https://edadeal.ru/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://kinopoisk.ru/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://turbopages.org/.well-known/related-website-set.json; error was: Expecting value: line 1 column 1 (char 0)
Experienced an error when trying to access https://webvisor.com/.well-known/related-website-set.json; error was: Expecting value: line 1 column 1 (char 0)
Experienced an error when trying to access https://ya.cc/.well-known/related-website-set.json; error was: HTTP Error 404: Not found
Experienced an error when trying to access https://yandex.az/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yandex.by/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yandex.com/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yandex.com.am/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yandex.com.ru/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yandex.kz/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yandex.md/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yandex.net/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yandex.ru/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yandex.st/.well-known/related-website-set.json; error was: HTTP Error 404: Not found
Experienced an error when trying to access https://yandex.tj/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yandex.tm/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yandex.uz/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://yastatic.net/.well-known/related-website-set.json; error was: HTTP Error 404: Not found

[IvanKharpalev]

Please, permanently delete this PR.