fixed url parsing for escaped chars

[parasharrajat]

Anyone, will you please review this?

[Explanation of the change or anything fishy that is going on]
We escape the input string before apply Rules from Expensimark but we forgot to check for the Escaped chars in the URL regex. I have updated that.
Apart from it, Added : to the regex so that it can be matched as part of the URL. Google Map URLs contain this.

Fixed Issues

$ Expensify/App#4105

Tests

1. What unit/integration tests cover your change? What autoQA tests cover your change?
   Unit test
2. What tests did you perform that validates your changed worked?
   I tried many URLs for matching and all seem to pass

QA

1. What does QA need to do to validate your changes?
   URLs should be parsed in E.cash.
2. What areas to they need to test for regressions?
   E.cash messaging

[parasharrajat]

@Jag96 Requesting review. Thanks.