feat(http-log): Add docs for logged header allow list

[ItsKaleb]

This PR adds the supporting documentation for PR #11427. Functional changes are to implement an allow list for which request/response headers should be included in log entries.

Description

Add supporting documentation for
Kong/kong#11427

Testing instructions

Netlify link:

Checklist

• Review label added
• PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

[netlify]

❌ Deploy Preview for kongdocs failed.

Name	Link
🔨 Latest commit	d419d1d
🔍 Latest deploy log	https://app.netlify.com/sites/kongdocs/deploys/64e40c21d0c51500075e0792

[acgoldsmith]

Hi @ItsKaleb , thanks for this PR. Could you please point to release/gateway-3.5 rather than main? Thanks.

[ItsKaleb]

Thanks @acgoldsmith, will do that, yep.

[ItsKaleb]

Hey @acgoldsmith, Vale seemed to be flagging some of the config field names as potential spelling errors. I've never used Vale before, is there a way to ignore those checks? I've also just updated the PR to address some of the legit findings it reported.
Thanks

[cloudjumpercat]

@ItsKaleb Thanks for fixing some of those Vale errors! I'm happy to help with the others.

I think maybe some extra commits were pulled in when the base branch was changed to release/gateway-3.5, so I think the easiest way to fix it would be for me to create a new PR for you and I can cherry pick the commits you specifically made. I think the only ones with doc changes you made were 8ca48b0 and 271cce1, correct? The rest were either rebases/updating the branch or commits accidentally pulled in, I think?

Then I can help by getting those config names added to our Vale ignore file so Vale ignores them.

[ItsKaleb]

Ah yes, thanks @cloudjumpercat
My apologies, I'm more familiar with Bitbucket than Github, so not surprised that I messed that up.
I'll do as you suggested and raise a new PR, should be able to sort that soon.

[cloudjumpercat]

@ItsKaleb No worries! If you'd like, I can always do the cherry pick to the new PR as well.

[ItsKaleb]

Just to provide an update, I'm currently working through some hiccups with the feature branch in the main repo. Once things are sorted there, I'll revisit this PR and get the docs for the new feature fixed up.

[Guaris]

I've removed the Gateway 3.5 milestone the corresponding PR does not look like it will be added to the 3.5 release
Kong/kong#11427

If I am incorrect please re-add the milestone and tag me.