Provide more clarity in UPDATE_LOG's warning

[danyalaytekin]

Consider making the UPDATE_LOG.md's warning more precise, since it is currently perhaps more worrying than necessary:

• attach a date to the warning, to allow a reader to understand what "URGENT" means
  • we can inspect the commit log to find the date, but this does not convey information about the freshness of the warning
• describe exactly what happened and how, and examples of groups which were affected and which were not affected, covering:
  • people who downloaded from this repo in GitHub
  • people who used in-app update functionality
  • package manager users e.g. Homebrew, Winget
  • example of forks or mirrors known to be corrupted

The documentation update could also touch on your suggestion in version 0.11.1's release notes to disable Apple's quarantine functionality to navigate the unusual damaged file warning.

[danyalaytekin]

For the damaged file warning, is this why it occurs, and why wasn't a similar warning produced by previous builds, or was that just a red herring and the warning is triggered only on newer versions of macOS?:

• https://github.com/tauri-apps/tauri/issues/5778