Write `bevy_lint` release checklist and changelog

[BD103]

This PR lays down the framework for bevy_lint's release process.

• It creates a release checklist, inspired by the engine's release checklist, for publishing a new version of bevy_lint.
• It creates a changelog that allow users to refer to changes between versions, based on Keep a Changelog. Large user-facing changes should be documented here with each PR.

Old argument on switching to 0.0.1, convinced otherwise and reverted

- Set `bevy_lint`'s version to `0.0.1-dev` instead of `0.1.0-dev`. This is mainly because: - `bevy_lint` will never be stable as long as `bevy` isn't stable, which means no 1.0 for now. - We cannot publish to because the project is not yet official and #150. - It would be strange if there were a series of minor 0.X releases missing from . - So instead we publish 0.0.X "alpha" releases, with corresponding instability warnings, just on Github.

[BD103]

cc @cart and @mockersf, since you both were involved discussing the release process.

[richchurcher]

TBH I'd just YOLO the minor releases, even if they aren't on crates.io, just because my brain always interprets 0.0.x as a patch release. But so long as we're consistent I guess it's a small point.

[BD103]

TBH I'd just YOLO the minor releases, even if they aren't on crates.io, just because my brain always interprets 0.0.x as a patch release. But so long as we're consistent I guess it's a small point.

Ok, point taken! I'll let others weight in before making a final decision.

[BD103]

I reverted the change to 0.0.1, so now the first release will continue to be 0.1.0.