Fix static scan issue by updating AES cipher mode

[Dilli-Babu-Godari]

Description

Changed AES cipher mode from AES/CBC/PKCS5Padding to AES/CTR/NoPadding.

Motivation and Context

Impact

Test Plan

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
*  Fix static scan issue by updating AES cipher mode :pr: '25603'

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Dilli-Babu-Godari (c7e897c)

[sh-shamsan]

Could you add a bit of background on what issue led to this switch? context would be nice in the PR description for future reference

[Dilli-Babu-Godari]

Could you add a bit of background on what issue led to this switch? context would be nice in the PR description for future reference

A static scan has flagged the issue that usage of padding leads to potiential security risks and to change it to a different encryption process. so I checked whether the AES/CBC has any NoPadding option to fix this but it doesn't provide with that option. so I went with AES/CTR it offers both NoPadding option and it doesn't compromise in terms of the encryption of data by updating to CTR.
It is actually safer than CBC mode.
https://crypto.stackexchange.com/questions/6029/aes-cbc-mode-or-aes-ctr-mode-recommended

[namya28]

Could you please ensure that all the CI checks pass.