helm: move verbose and sign args outside artifactory check

[blink-so]

This PR fixes an issue where the --verbose and --sign arguments were only applied when artifactory was disabled.

Changes:

• Moved --verbose and --sign argument blocks outside of the artifactory.enabled if-else statement
• These arguments now apply regardless of artifactory configuration

Before: Arguments were only added when persistence.artifactory.enabled was false
After: Arguments are added based on verboseLogging and extensionSigning values regardless of artifactory configuration

Resolves the issue described in lines 75-80 of helm/templates/deployment.yaml.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[blink-so]

The CLA Assistant check is failing because the bot account needs to sign the CLA. This is expected for automated contributions. A human maintainer can bypass this check when reviewing the PR, or the bot account can be added to the CLA allowlist if desired.

The actual code changes have passed the helm linting checks successfully. ✅