Request: Add a 'Path Type' section in the Guide > Ingress section of the live 'Annotations' docs.

[WyWyFe]

Is your feature request related to a problem?
Per private offline discussion with @kishorj, it may be helpful to add a "Path Type" section in the Guide > Ingress section of the live docs here.

Currently, as @kishorj explained, prior to v2.4.3, listener rules follow the order specified in the manifest.
Beginning from v2.4.3 of the AWS LBC,
"ImplementationSpecific rules are always ordered according to the rule order in the manifest.
However, in case of mixed path types,

• exact match are always ordered first
• followed by prefix paths with longest prefix first
• implementation specific paths in the order from the manifest."

This information is also explained elsewhere on previous GitHub issues, but it would be very helpful for customers to see a detailed summary of the path type ordering logic pre- and post-v2.4.3 in a 'path type' section in the live docs.

Describe the solution you'd like
If the team could add a "Path Type" section in the Guide on the live docs for Ingress annotations explaining path type ordering logic as well as the path type implications, this would increase visibility for customers and also provide a convenient way to view this information.

Describe alternatives you've considered
A blog post discussing path types for ingress objects and implications with different versions of the AWS LBC could also help!
Any other suggestions are appreciated. :)

[kishorj]

/kind documentation