ignores routing as per rid if the value is anti-csrf

[rishabhpoddar]

Summary of change

Ignores routing based on rid if the value of it is "anti-csrf"

Related issues

• Manually calling APIs without adding the correct RID header can result in a 404 #202

Test Plan

Check various rids being used against APIs that exists / don't exist and them yielding proper status codes.

Documentation changes

No change required

Checklist for important updates

• Changelog has been updated
• coreDriverInterfaceSupported.json file has been updated (if needed)
  • Along with the associated array in lib/ts/version.ts
• frontendDriverInterfaceSupported.json file has been updated (if needed)
• Changes to the version if needed
  • In package.json
  • In package-lock.json
  • In lib/ts/version.ts
• Had run npm run build-pretty
• Had installed and ran the pre-commit hook
• Issue this PR against the latest non released version branch.
  • To know which one it is, run find the latest released tag (git tag) in the format vX.Y.Z, and then find the latest branch (git branch --all) whose X.Y is greater than the latest released tag.
  • If no such branch exists, then create one from the latest released branch.
• If have added a new web framework, update the add-ts-no-check.js file to include that
• If added a new recipe / api interface, then make sure that the implementation of it uses NON arrow functions only (like someFunc: function () {..}). If creating a sub recipe, make sure to use bind(this) when calling the original implementation from your functions

Remaining TODOs for this PR

• Tests