Add generic fuzzy matching logic to the database layer

[haixin]

share list, share snap list, Fuzzy query by name or description is supported, but the current implementation is first get all the shares, then In the API layer, the for loop is used to achieve fuzzy matching, if the num of shares is big,
It will seriously affect the speed of fuzzy matching.Therefore, we should let the database do the matching to speed up the query.
   i also noticed that in share snap list api, Paging query parameters limit and offset same problem with fuzzy queries,we also need to move those to database layer to deal with it.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/734041

[Vida Haririan (vhariria)]

Additional comments Additional comments https://meetings.opendev.org/meetings/manila/2021/manila.2021-06-17-15.00.log.html

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/manila/+/734041
Committed: https://opendev.org/openstack/manila/commit/e032c13bfb0d2ee2bc3c6d4b2adda27b6759a14b
Submitter: "Zuul (22348)"
Branch: master

commit e032c13bfb0d2ee2bc3c6d4b2adda27b6759a14b
Author: haixin <email address hidden>
Date: Mon Jun 8 17:08:51 2020 +0800

    Add generic fuzzy matching logic to the database layer

    share snap list, Fuzzy query by name or description is supported, but
    the current implementation is first get all the shares, then In the API
    layer, the for loop is used to achieve fuzzy matching, if the num of
    shares is big,
    It will seriously affect the speed of fuzzy matching.Therefore, we
    should let the database do the matching to speed up the query.
    Moving the pagination params (limit, offset, sorting) to the database
    layer for snapshot list, to optimize query speed.

    Closes-Bug:#1881865
    Partial-Bug:#1831094

    Change-Id: I283e78c9e7c2dd626d94cf6c1b01d4e2f9ae8097

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/manila 13.0.0.0rc1 release candidate.