Fixed importing savepoints

[grzesiek2010]

Closes #6405

Why is this the best possible solution? Were any other approaches considered?

There is not much to discuss here. The form name should be escaped so that it is treated as literal text when used in a regular expression pattern.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

I've only modified the regex used to identify savepoints associated with the given form names. This change shouldn't affect the existing implementation, it simply resolves the issue.

Here are the apks for testing: https://drive.google.com/file/d/14hDAkrEGU6MoGZsj3cJDorib9KnuEZzL/view?usp=sharing

Do we need any specific form for testing your changes? If so, please attach one.

No.

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No.

Before submitting this PR, please make sure you have:

• added or modified tests for any new or changed behavior
• run ./gradlew connectedAndroidTest (or ./gradlew testLab) and confirmed all checks still pass
• added a comment above any new strings describing it for translators
• added any new strings with date formatting to DateFormatsTest
• verified that any code or assets from external sources are properly credited in comments and/or in the about file.
• verified that any new UI elements use theme colors. UI Components Style guidelines

[dbemke]

Tested with Success!

Verified on a device with Android 10

Verified Cases:

• issue Incorrectly nested parentheses in regexp pattern #6405 doesn't occur after upgrades to master with a form added manually to a project

[WKobus]

Tested with Success!

Verified on device with Android 14