[BUG]: Plugin Fails to Scan and Add Cards with Trailing Spaces After the First or Second Line for Block Cards

[Leegenux]

Description:
The plugin ignores cards that contain space characters after either the first or second line. This issue prevents legitimate cards from being added.

Steps to Reproduce:

Attempt to add a card with the following content, noting the trailing spaces after the first line:

START 
Basic
HTTP Header Fields
Back:
- HTTP defines various header fields, used to carry metadata for requests and responses.
- Header fields can include general header fields, request header fields, response header fields, and entity header fields.
END

Expected Result:
The card is successfully scanned and added to the vault without issues.

Actual Result:
The plugin fails to recognize and add the card due to the trailing space characters.

Rationale for Fixing:
Ensuring the plugin can handle cards with accidental trailing spaces is crucial for maintaining a robust and user-friendly experience. Cards that appear legitimate should not be excluded from the vault due to such minor formatting discrepancies. Fixing this issue will enhance the plugin's reliability and prevent users from missing important content due to unnoticed trailing spaces.