Update coindesk ToS selector

[Cli4d]

I updated Coindesk Terms of Service selectors to reduce cases of blinking in tracking changes. I have not included a history.json file since I am not sure how to get the valid until date, as it is supposed to be the last snapshot time and date, but this service continues its tracking. Maybe you can provide more direction here

[clementbiron]

Hi Clifford

Thanks for the pull request, it will be great to fix this blink 👍

I've taken the liberty of improving the selector, although your .flex-grow proposal works, I think it might be less stable because it's a generic class name that could be used repeatedly on non-meaningful content.

I also added the history and to do this I searched in the version history of this document for the commit that preceded the introduction of the blink. I think it's this one OpenTermsArchive/contrib-versions@69d2440
It's an appromixation because the commit contains both the blink and the meaningful change, but it seems acceptable to me.

From that commit, i found the validUntil date by inspecting the Nov 25, 2024 date.

[Cli4d]

Hi Clifford

Thanks for the pull request, it will be great to fix this blink 👍

I've taken the liberty of improving the selector, although your .flex-grow proposal works, I think it might be less stable because it's a generic class name that could be used repeatedly on non-meaningful content.

I also added the history and to do this I searched in the version history of this document for the commit that preceded the introduction of the blink. I think it's this one OpenTermsArchive/contrib-versions@69d2440 It's an appromixation because the commit contains both the blink and the meaningful change, but it seems acceptable to me.

From that commit, i found the validUntil date by inspecting the Nov 25, 2024 date.

Thanks so much for this review @clementbiron. At least it sheds more light on how to best handle blink PRs, and especially getting a valid until date. Thank you

I'll apply this information to any more PRs that I open