Fix parsing issue when a backslash as the last character on sudoers file line

[iko1]

This PR fixes the bug reported at #7421. I handle the case that a line contains a backslash as last character.
The code aggregates multiple lines within a "rule_details" column. The aggregation logic starts when a line ends with backslash and end when EOF or the next line doesn't end with a backlash.
The code deletes the backslash character in favor of clearness.
Any feedback is more than welcome, Thanks!

[mike-myers-tob]

Looks good to me (I reviewed, but don't have the ability approve a PR)

[sharvilshah]

Hey @iko1, thanks so much for this! Do you think we need to add/update the sudoers_test to handle this case?

[iko1]

Hey @iko1, thanks so much for this! Do you think we need to add/update the sudoers_test to handle this case?

@sharvilshah, Indeed, the change should be covered in unit test. I'm thinking about adding the following tests:

1. Trivial case when a long line exists in a line that doesn't start with '#'
2. Line that starts with '#' and end with blackslash should be parsed as a single line.

If you have any other edge cases that should be covered, please elaborate them here

[sharvilshah]

Hey @iko1, thanks so much for this! Do you think we need to add/update the sudoers_test to handle this case?

@sharvilshah, Indeed, the change should be covered in unit test. I'm thinking about adding the following tests:

1. Trivial case when a long line exists in a line that doesn't start with '#'
2. Line that starts with '#' and end with blackslash should be parsed as a single line.

If you have any other edge cases that should be covered, please elaborate them here

Those sound great, thanks!

[sharvilshah]

Looks good, thanks