Remove BOMs from analytics v2

[pemontto]

This was previously discussed in #1339 but it seems like it's not yet handled in validations.

Change(s):

• Some analytics have byte order marks (BOM). This can make working with them unpredictable.

Reason for Change(s):

• consistency
• prevent breaking pipelines

Version Updated: No, not required. This is a non-functional change and we'd expect to see the rule version pipeline fail.

Testing Completed: ✅

[v-prasadboke]

Hello @pemontto, I dont see much changes in the files

[pemontto]

It won't look like much as it's removing invisible byte order marks. They really shouldn't be in these files. See previous discussion - #1339 (comment)

[v-prasadboke]

Hello @pemontto, I got it what you are trying to say here.

But when a solution is getting packaged the packaging tool automatically resolve this issue.

You can try it on your end by packaging a solution locally on your system
Please go through this documentation on how to use V3
https://github.com/Azure/Azure-Sentinel/blob/master/Tools/Create-Azure-Sentinel-Solution/V3/README.md

[v-prasadboke]

I suggest you to please close on this PR

[v-prasadboke]

We wanted to check on the status of PR #11261. PR is pending for more than 10+ days. Please let us know if you need any assistance to review this PR. Per our standard operating procedures if no response is received in the next 7 business days, we will close this PR. Thank you for your cooperation.

[v-prasadboke]

Since we have not received a response in the last 7 days, we are closing your PR #11261 per our standard operating procedures. If you still need support for this issue, you can re-open the PR at any time.

If you do re-open, we simply request that you ensure the PR has response to the last request. Thank you for your cooperation.