Remove access token from RouteOptions

[LukasPaczos]

Refs #1265, #1267, and #1270 where we tightened the RouteOptions integration while also stopped serializing the access token for security reasons. In mapbox/mapbox-navigation-android#4662 (comment) we were discussing the implications and potential improvements.

We should be able to entirely remove the access token from the RouteOptions to avoid the problems of deserialization and usability of route objects. Each entity that does need to make a resources request using a route reference (like annotations refresh or reroute) will most likely get a token from a different source, the route object shouldn't need to transport it.