Add documentation for security config upgrade feature

[peternied]

Description

Adds documentation for the new security feature to upgrade configurations based on the default config files bundled with the security plugin

Issues Resolved

• Resolves [DOC] Add documentation for security configuration upgrade feature #6633

Checklist

• By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
  For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[hdhalter]

Thanks, @peternied! Can you please address the Vale errors prior to the doc review? Thanks.

[cwperks]

Thank you @peternied. Left a few comments.

[cwperks]

@peternied I left 2 comments, but otherwise this looks good to me and can go for editorial review.

[DarshitChanpura]

Left a couple of comments. Looks good to me otherwise.

[natebower]

@peternied @Naarcha-AWS Please see my comments and changes, particularly my comment on line 1305, and let me know if you have any questions. Thanks!

[natebower]

There appear to be some words missing in the second sentence.

[peternied]

Original text: Checks the configuration bundled with the Security plugin against the existing security configuration, returns if an upgrade can be performed and what resources would be updated.

Here is a diagram of what the actual flow / comparisons are. (Thanks ChatGPT!)

sequenceDiagram
    participant U as User
    participant D as Configuration on Disk
    participant S as SecurityPlugin
    participant M as Configuration in SecurityPlugin Memory
    U->>+S: API Call to Check Configuration
    S->>+D: Retrieve Current Configuration from Disk
    D-->>-S: Current Disk Configuration
    S->>+M: Check Configuration in Memory
    M-->>-S: Current in Memory Configuration
    S->>S: Compare Configurations
    alt Configurations Match
        S-->>U: No Update Needed
    else Configurations Do Not Match
        S->>S: Determine Resources for Update
        S-->>U: Update Can be Performed, List resources to Update
    end

Loading

[peternied]

@natebower I feel like that original text might be a better starting point, but let me know if you'd like me to workshop it more

[Naarcha-AWS]

@peternied: I think I'm confused as to what you mean by "bundled"? When I hear bundled, I assume the API is checking for upgrades either against the upstream instance (The newest artifact) or the version the artifact the user downloaded. But, if the user has to download a new artifact for the latest Security Plugin information to persist in memory, isn't there a step we're missing in the documentation then?

[peternied]

I mean the version the artifact the user downloaded.

This API is for after an upgrade was performed, such as a Rolling Upgrade.

Note; I think this highlights another part of the documentation that I should include 'now that you've upgraded you can [optionally] upgrade the security configuration via this API' which links to this documentation

[natebower]

"cluster operator" (singular)?