Correct Azure localization issues

[bserocki-splunk]

Details

Three Azure detections currently use operationName.localizedValue; this value appears in the initiating user's current language setting, so there is a risk of false negative detections if we key off of this value in the signature. Correcting the three detections to use the relevant values in the operationName.value field to prevent this risk.

index=* `azure_audit` | stats count by operationName.value operationName.localizedValue | where NOT match('operationName.localizedValue', "^[\x20-\x7E\x09-\x0A]+$")

Reference: https://learn.microsoft.com/en-us/rest/api/automation/operations/list

Old Value	New Value
operationName.localizedValue="Create or Update an Azure Automation account"	operationName.value="Microsoft.Automation/automationAccounts/write"
operationName.localizedValue="Create or Update an Azure Automation Runbook"	operationName.value="Microsoft.Automation/automationAccounts/runbooks/write"
operationName.localizedValue="Create or Update an Azure Automation webhook"	operationName.value="Microsoft.Automation/automationAccounts/webhooks/write"

Checklist

• Validate name matches <platform>_<mitre att&ck technique>_<short description> nomenclature
• CI/CD jobs passed ✔️
• Validated SPL logic.
• Validated tags, description, and how to implement.
• Verified references match analytic.
• Confirm updates to lookups are handled properly.

Notes For Submitters and Reviewers

• If you're submitting a PR from a fork, ensuring the box to allow updates from maintainers is checked will help speed up the process of getting it merged.
• Checking the output of the build CI job when it fails will likely show an error about what is failing. You may have a very descriptive error of the specific field(s) in the specific file(s) that is causing an issue. In some cases, its also possible there is an issue with the YAML. Many of these can be caught with the pre-commit hooks if you set them up. These errors will be less descriptive as to what exactly is wrong, but will give you a column and row position in a specific file where the YAML processing breaks. If you're having trouble with this, feel free to add a comment to your PR tagging one of the maintainers and we'll be happy to help troubleshoot it.
• Updates to existing lookup files can be tricky, because of how Splunk handles application updates and the differences between existing lookup files being updated vs new lookups. You can read more here but the short version is that any changes to lookup files need to bump the the date and version in the associated YAML file.

[ljstella]

@bserocki-splunk Thanks for moving this over! Appinspect failures are expected for PRs from forks, so you can ignore that.

[patel-bhavin]

@bserocki-splunk : the logic behind the change seems sound! Thank you for this PR and fixing the detections. If you'd like please feel free to add your name to the author section

Thank you!