Add missing entry in Changelog

[ket395]

3.43.4...3.43.5

I am grateful that the tag comparison links are provided but a changelog file for a VSCode extension usually/normally/typically contains an entry for the latest public version at the top rather than below. And it clearly mentions any notable changes or fixes. The lack of such helpful information strongly discourages an educated user from installing the extension. It's easier to find a replacement or patch/hack it for minor fixes with tangible benefits.

This current release lacks it. And i suspect this is a trend with this single repo.

dishonest commit message - Revert "fix: move extended language formatting to client"

The PR explaining my use of the adjective - #1261

Horribly managed projects that can't be trusted at first glance do have this idea/opinion/delusion that commits are only for technical people who have lots of or unreasonable amounts of free time to spend on each lil OSS or otherwise project, and thus commits should not have a description in some cases. The referenced commit would have been perfectly fine if the assumptions made by the commiter and the assumptions of the potential reader/reviewer of the commit matched but they don't. To reiterate, the commit message needs to briefly mention why the revert was neeeded/done. To save his precious time the committer could have just pasted this text in the commit description

Got a report that the extension was completely removing the contents of files.
Reverts https://github.com/denoland/vscode_deno/pull/1258

Or with one more line -

reverts pull/1258 - fix: move extended language formatting to client #1258 

That's all. The benefits are as obvious as the presence of harmful elements in a locale with a 301+AQI, use your intuition. And elderly and youths with respiratory illnesses.

PS - I'll update deno once I am sure it won't break my code or totally wreck my professional or informal workflow. It's already happened once. So I suggest new users be very cautious and meticulous.
PS - Yes, I just noticed the double entry in the changelog.
Manish