Update release_notes.md in dev branch for new release (v4.1037)

[castrodd]

Issue describing the changes in this PR

We have pushed the latest changes in dev to release/4.1037. Therefore, the Release Notes here on the dev branch need to be cleared.

Pull request checklist

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

• Backporting to the in-proc branch is not required
  • Otherwise: Link to backporting PR
• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• My changes do not require diagnostic events changes
  • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
• I have added all required tests (Unit tests, E2E tests)

[amamounelsayed]

[like] Ahmed El Sayed (MAMOUN) reacted to your message:

…

________________________________ From: Daniel Castro ***@***.***> Sent: Monday, December 2, 2024 10:16:21 PM To: Azure/azure-functions-host ***@***.***> Cc: Ahmed El Sayed (MAMOUN) ***@***.***>; Comment ***@***.***> Subject: Re: [Azure/azure-functions-host] Update release_notes.md in `dev` branch for new release (v4.1037) (PR #10658) Merged #10658<#10658> into dev. — Reply to this email directly, view it on GitHub<#10658 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMOXONARXUJCNUFIJPYYQYD2DTL3LAVCNFSM6AAAAABS35SBEOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGUYDAMJTGQYTMMY>. You are receiving this because you commented.Message ID: ***@***.***>