Improve error message if data dir on tbot and tctl not available for permissions

[stevenGravy]

This matches the error message given in teleport start for tctl and tbot when not running with access to data dir. This matches to similar message when running teleport start

Currently:

$ tctl users ls                     
# ERROR: lstat /private/var/lib/teleport/host_uuid: permission denied`

$ tbot start --auth-server=server
# ERROR: stat /var/lib/teleport/bot: permission denied

Now

$ tctl users ls
ERROR: Teleport does not have permission to read Teleport host UUID file at /var/lib/teleport/host_uuid. Ensure that you are running as a user with appropriate permissions.
lstat /private/var/lib/teleport/host_uuid: permission denied

$ tbot start --auth-server=server
ERRO [TBOT]      Teleport does not have permission to write to: /var/lib/teleport/bot. Ensure that you are running as a user with appropriate permissions. config/destination_directory.go:132
ERROR: stat /var/lib/teleport/bot: permission denied

[stevenGravy]

@zmb3 added you as you were part of the original error message review on #10044

[zmb3]

A couple comments:

1. Why the inconsistency? In tbot we are logging an enhanced error message, but returning the original error unmodified. In tctl we are wrapping the original error with a better message. Can we be consistent and take the same approach in both places?
2. You shouldn't need to use fmt.Sprintf here. trace.Wrap already supports this: trace.Wrap(err, "this is a message: %v", x)

[stevenGravy]

thanks @zmb3 I've made these consistent approaches and removed the unnecessary fmt.Sprintf. Please check when you can.

[zmb3]

This might confuse a user, as you'll log the error here, but also return a [different] error, which will eventually also be logged.

In general you should handle an error either by logging it or returning it, but not both.

[zmb3]

We're nearly there.

[zmb3]

In this case, we weren't trying to write, so the error message is not correct.

I would say something like does not have permission to access %v.

[stevenGravy]

@zmb3 changed error message and applied other suggestions

[github-actions]

@stevenGravy See the table below for backport results.

Branch	Result
branch/v10	Create PR
branch/v9	Create PR