fix: 🐛 fixes for \n characters in inappropriate places and parsing bug

[bile0026]

Fix bad logic with line.startswith.
Add clean function to handle when lines are inappropriately split between double quotes in some backup files.

[itdependsnetworks]

Just a note for review, this is an example of a newline inserted.

[qduk]

Hey @bile0026. Thanks for the PR. Can you add tests for palo_alto_clean_newlines that show the following:

• When no newline is used.
• What happens when a match is found? e.g. does it concatenate it to a single line?
• How does this affect the compliance?

[bile0026]

Hey @bile0026. Thanks for the PR. Can you add tests for palo_alto_clean_newlines that show the following:

• When no newline is used.
• What happens when a match is found? e.g. does it concatenate it to a single line?
• How does this affect the compliance?

Added tests for the first 2. Yes, it finds the rest of the line up to the " and concatenates it to a single line.

This is specific to when there's a \n character between quote marks "". These aren't supposed to be there but if a user copy/pastes a config into the GUI it will allow it. If these \n characters are in the backup config it breaks compliance rules and never shows up in the Golden Config section because GC ends up treating it like a new config section because it drops it to a new line without indentation.

this is a config line {
    section1 {
        configuration line
drops to a new line with no indent;
        next configuration line;
    }
}   

[itdependsnetworks]

@qduk will merge by friday unless you have a concern.

[qduk]

LGTM