Fix tests based on more clarification on RSA7e

[sacOO7]

• RSA7e specifies if clientOptions.clientId and basic auth provided, set clientId as a header/queryparam although server accepts clientId on connection for token auth.
• Link to internal conversation -> https://ably-real-time.slack.com/archives/C8SPU4589/p1720167508719079
• In favor of seeking more clarity, two tests are skipped

1. Ably::Realtime::Connection using JSON protocol intialization with token auth with opaque token string that contain an implicit client_id string that is incompatible with the current client client_id fails the connection
2. Client using MsgPack protocol initialization token auth with a Proc for the :auth_callback option with a wildcard client_id token and an explicit client_id in ClientOptions allows uses the explicit client_id in the connection

┆Issue is synchronized with this Jira Task by Unito

[sacOO7]

Previous related issue #414

[sacOO7]

Clarification using spec PR -> ably/specification#195