This PR updates all the necessary files for 2.0.1 release.

Problem: When a BackendRef filter is specified in a Route, the control plane crashes due to an index out of range error.

Solution: Fix the way we build the filter list so we don't access an undefined index.

Problem: There's a specific scenario where we can hit an out of bounds index while building route statuses. I don't know the exact scenario, but it involves a parentRef without a sectionName, on a Gateway with a single listener. Could possibly involve having multiple implementations being deployed as well.

Solution: Adjust the logic to ensure we don't access indices that are out of bounds.

Move automountServiceToken to Pod

Problem: For security reasons, it's best practice to not have `automountServiceToken` on the ServiceAccount, and instead set in directly on the workloads that need the token.

Solution: Set this field on the Pods instead of the ServiceAccounts.

Problem: The nginx deployment was using extra privileges in order to bind to privileged ports (<1024). This included `allowPrivilegeEscalation` and `NET_BIND_SERVICE`. Sometimes this could cause issues in some secure environments.

Solution: Remove these extra privileges and take advantage of `sysctls` to lower the allowed port range for the pod its defined on.

#3592)

fix: removes Extra keyword from volumeMounts and Volumes for the data… (#3588)

fix: removes Extra keyword from volumeMounts and Volumes for the data plane

Co-authored-by: Vishal Vazkar <[email protected]>

Problem: SnippetsFilters are being included in NGINX configuration for all gateways regardless of whether routes attached to those specific gateways actually referenced the filters.

Solution: Implemented gateway-specific scoping by adding GetReferencedSnippetsFilters() method that returns only SnippetsFilters referenced by routes attached to the current gateway.

Update all necessary files in the release branch for 2.0.2.