fix(AIP-133): lint http collection ID for lookalikes

[noahdietz]

If there is a Custom Method that looks like a Standard Create e.g. CreateAndCheckoutBook, it will have a HTTP suffix like .../books:createAndCheckout. For a resource path like books/{book} this would be valid, sans custom method suffix, because the collection IDs match at the end of the HTTP path, but the rule naively included the custom method suffix and expects the resource pattern to look like books:createAndCheckout. While using Standard Method verbs for Custom Methods is not allowed, it happens occasionally, and ApiLinter shouldn't emit garbage as a result.

Address internal issue.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.