fix: replace Buffer operations with string methods to resolve deprecation warning

[BrenoRev]

#30

Issue Fixed
This change addresses the Node.js deprecation warning:

What Changed
Replaced Buffer-based operations in the sanitize() function with pure string methods to eliminate deprecated Buffer constructor usage. The implementation now uses JavaScript's native string operations (split(), filter(), and join()) while maintaining the same XML character filtering behavior.

Benefits
Eliminates deprecation warnings that were causing Lambda function failures
Maintains the same output as the previous implementation
Improves security by avoiding potential Buffer-related vulnerabilities
Better handles edge cases (null/undefined values)

[BrenoRev]

@jancurn @gippy any update?

[gippy]

@jancurn @gippy any update?

Sorry, this sprint is pretty busy, I'm planning to check this PR around Wednesday next week.

[BrenoRev]

@jancurn @gippy any update?

Sorry, this sprint is pretty busy, I'm planning to check this PR around Wednesday next week.

ok

[BrenoRev]

@gippy any update?

[jancurn]

I'm bit afraid this could have a performance impact, as the buffer had pre-allocated size, while the string concatenation does not...

[BrenoRev]

I'm bit afraid this could have a performance impact, as the buffer had pre-allocated size, while the string concatenation does not...

Is there any solution to remove the Buffer?

[BrenoRev]

@jancurn How could i help?

[jancurn]

Is there some way to just ignore the deprecation warning or use some other Buffer constructor, but keep the logic as is? We need to be sure this will not negatively affect the performance