Editorial: drop Changes section

[marcoscaceres]

This section adds limited value that one can't get from the actual commit history. The document already links to the commit history in the head. It's also hassle for editors to maintain.

We should as Bikeshed to generate this section automatically once it supports such a thing... same a ReSpec does, with link to the appropriate PRs etc.

---

Preview | Diff

[anssiko]

This section is in place to satisfy https://www.w3.org/2023/Process-20231103/#transition-reqs for our upcoming CR Snapshot publication as communicated in the CfC sent to both the groups: https://lists.w3.org/Archives/Public/public-device-apis/2024Mar/0000.html

In a chair capacity, I'll ask the editors to make sure this section is updated to reflect the latest changes, and not removed. Please open a new PR for that. Thank you for your contributions that help explain this specification's journey to its readers.

[himorin]

@marcoscaceres I support an idea that bikeshed should have a feature to auto-generate changes or commit history section, with breaking into periods like during WD or between two CRS, but I cannot support this PR to remove existing list before bikeshed supports and configuration included in this PR.

[reillyeon]

I filed a feature request for this in Bikeshed: speced/bikeshed#2847