Enable StatusString for all readers

[greedy52]

Related

• Reapply: Fix an issue status type (+) is not read/write properly  #37
• AWS Redis ElastiCache 7.0.7 Engine Version failing to connect: ERROR: signal: aborted (core dumped) teleport#33564

In #37, a readerOpt was added as an option to enable StatusString to workaround UT issues. However, this means the default connection pool does NOT have this flag ENABLED, thus making the original StatusString fix USELESS. 😭

This PR reverted the readerOpt part and fixed the other UTs properly.

I did consider pushing the StatusString fix upstream but it's clear that this breaks backward compatibility as cmd.Val() will return a proto.StatusString instead of string.

Will need to revisit later to see if possible to make an upstream acceptable version of the fix or maybe fix this entirely on the Teleport side without driver change.

Also there are some testing escapes. Will add a "COMMAND DOCS" test at a higher level in teleport repo. And for e2e testing, we should always test out a user with full permission (I didn't catch this because my users do not have COMMAND DOCS permission to trigger this case)

[greedy52]

friendly ping @jentfoo 😃

[jentfoo]

Good catch @greedy52, thank you for continuing to think on this issue.