Update default backend to add TLS >=1.2 support

[JJotah]

What this PR does / why we need it:

Security issue with TLS https://github.com/kubernetes/ingress-nginx/issues/9155

Types of changes

• [X] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] CVE Report (Scanner found CVE and adding report)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation only

Which issue/s this PR fixes

https://github.com/kubernetes/ingress-nginx/issues/9155

How Has This Been Tested?

• Deploy this helm chart
• Point to the default backend
• Execute nmap --script ssl-enum-ciphers -p PORT with the URL

Checklist:

• [X] My change requires a change to the documentation.
• [X] I have updated the documentation accordingly.
• [X] I've read the CONTRIBUTION guide
• [X] I have added unit and/or e2e tests to cover my changes.
• [X] All new and existing tests passed.
• [X] Added Release Notes.

Does my pull request need a release note?

Any user-visible or operator-visible change qualifies for a release note. This could be a:

• CLI change
• API change
• UI change
• configuration schema change
• behavioral change
• change in non-functional attributes such as efficiency or availability, availability of a new platform
• a warning about a deprecation
• fix of a previous Known Issue
• fix of a vulnerability (CVE)

No release notes are required for changes to the following:

• Tests
• Build infrastructure
• Fixes for unreleased bugs

For more tips on writing good release notes, check out the Release Notes Handbook

### 4.4.0
- Update Default Backend due TLS < 1.2 Security Issue