Updated documentation to reflect the correct order of deletion for ingress-related resources

[praddy26]

Issue

Fixes #4341

Description

This PR adds documentation about the correct order of deletion for AWS Load Balancer Controller resources, particularly around Ingress and IngressClass resources. The issue arises when users delete IngressClass resources before deleting the associated Ingresses, resulting in orphaned Ingress resources that cannot be cleaned up without manual intervention.

Changes made:

• Added a new section "Resource Cleanup Order" in docs/guide/ingress/ingress_class.md
• Clearly documented the recommended order of deletion (Ingresses first, then IngressClass/IngressClassParams)
• Explained why this order is important and the consequences of incorrect deletion order
• Used consistent documentation style with existing content (MkDocs admonitions)
• Added warning block to highlight potential issues

Checklist

• Added/modified documentation as required (such as the README.md, or the docs directory)
• Manually tested (verified documentation renders correctly with MkDocs)
• Made sure the title of the PR is a good description that can go into the release notes

BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯

• Backfilled missing tests for code in same general area 🎉
• Refactored something and made the world a better place 🌟

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: praddy26
Once this PR has been reviewed and has the lgtm label, please assign shraddhabang for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @praddy26. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.