fix: handle phrases with apostrophes

[Agrendalath]

Description

We're using shlex to split phrases. It uses the POSIX mode by default, which is throwing an exception when there are unclosed quotes in phrases. This escapes such quotes, so the phrases with apostrophes can be split correctly.

Supporting information

OSPR ticket: OSPR-6172
OpenCraft Jira ticket: BB-4994

Known issues

The ElasticSearch connection was not working for me with the most recent devstack version. I had to add this to lms/envs/private.py and cms/envs/private.py:

ELASTIC_SEARCH_CONFIG = [
    {
        'use_ssl': False,
        'host': 'edx.devstack.elasticsearch710',
        'port': 9200
    }
]

Testing instructions

1. Enable FEATURES['ENABLE_COURSEWARE_SEARCH'] in LMS.
2. Enable FEATURES['ENABLE_COURSEWARE_INDEX'] in Studio.
3. Create a Blank Common Problem XBlock with the following content:

   This should not have failed.
   This shouldn't have failed.
   This shouldn't've failed.
   This shou'dn't've failed.
   

4. Go to your dashboard in LMS and search for the following phrases:
   • "should not"
   • shouldn't
   • shouldn\'t
   • "shouldn't have"
   • shouldn\'t\'ve
   • "shouldn't've failed"
   • shou'dn't've
   • shou\'dn\'t\'ve
   • "shou'dn't've failed"

Deadline

"None"

Reviewers

• @alfredchavez
• edX reviewer (TBD)

[openedx-webhooks]

Thanks for the pull request, @Agrendalath! I've created OSPR-6172 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[natabene]

@Agrendalath Thank you for your contribution. Please let me know once this is ready.

[alfredchavez]

👍🏽

• I tested this: checked that the code works as expected(following described steps)
• I read through the code

[Agrendalath]

@natabene, this is ready for your review.
cc: @giovannicimolin, would you mind adding this to the OSPR list?

[giovannicimolin]

@Agrendalath I've added this one and https://github.com/edx/edx-platform/pull/29106 to the OSPR list.
With the recent changes in the community roles, @nizarmah is the new OSPR liaison assignee.

[Agrendalath]

@natabene, just a friendly reminder about this PR. It only handles an error that occurs when there is an uneven number of quotes in a search query.

[idegtiarov]

Thank you for the PR.

LGTM!

[openedx-webhooks]

@Agrendalath 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.

[Agrendalath]

Thanks for a quick review, @idegtiarov!