Add support for new Route Search API

[Ahmedhossamdev]

You can learn about the route search API here: https://developer.onebusaway.org/api/where/search/route

User story

As a developer,
I want to perform full text searches for route names,
so I can provide a better experience to my users.

Implementation notes

• We should use SQLite's built-in full text search capabilities instead of adding a separate search engine:
  https://www.sqlite.org/fts5.html
• Follow existing patterns for writing new APIs and API tests.

Acceptance criteria

• Maglev responds to requests for:
  GET /api/where/search/route.json?input={input}&key={key}

• The schema of Maglev's response format for this endpoint is identical to the current server's format
  (data will differ between servers by definition).

• Full test coverage exists for the endpoint.

• The feature is implemented in a manner that follows the best practices used by other Maglev API endpoints.

[aaronbrethorst]

thanks for logging this @Ahmedhossamdev!

[Bhup-GitHUB]

@Ahmedhossamdev would love to work on this!

[Ahmedhossamdev]

@Bhup-GitHUB Done

[Syed-Suhaan]

Hey! I would like to work on this issue if it is still open!

[Ahmedhossamdev]

@Syed-Suhaan Can you check the other issues?