On QueryRouterParserError queries will go to role "any" (primary or replica) instead of default_role or primary

[gcsabbagh]

Describe the bug
We have some queries that are failing parsing, and you would expect that they'd fall back to the primary, or at least the default_role set but instead they are being load balanced across primary and replica.

To Reproduce
Steps to reproduce the behavior:

1. Create a pool with the following config:

[pools."your_pool"]
pool_mode = "transaction"
load_balancing_mode = "loc"
default_role = "primary"
query_parser_enabled = true
query_parser_read_write_splitting = true
primary_reads_enabled = true

2. Execute a query that might fail parsing
3. Observe where query is routed. You will notice it is load balanced across primary or replica

Expected behavior
The query should be routed to primary or default_role

[gcsabbagh]

I think we need to either set the active_role to primary or set to the configured default_role here:

pgcat/src/client.rs

Line 972 in b37d105

Err(error) => {

I think primary would be safer.

@drdrsh thoughts?