Performance test for keyring

[suzuki-shunsuke]

• feat: get a GitHub Access Token from keyring #3174

If aqua gets a GitHub Access Token from keyring, the performance makes worse.
So aqua exec should access kerying only when it is necessary.

$ hyperfine -N --warmup 3 '/Users/shunsukesuzuki/go/bin/aqua which mkghtag' '/Users/shunsukesuzuki/.local/share/aquaproj-aqua/bin/aqua which mkghtag'
Benchmark 1: /Users/shunsukesuzuki/go/bin/aqua which mkghtag
  Time (mean ± σ):      59.1 ms ±   3.3 ms    [User: 41.1 ms, System: 9.5 ms]
  Range (min … max):    55.0 ms …  68.6 ms    52 runs
 
Benchmark 2: /Users/shunsukesuzuki/.local/share/aquaproj-aqua/bin/aqua which mkghtag
  Time (mean ± σ):      32.9 ms ±   2.7 ms    [User: 33.0 ms, System: 3.6 ms]
  Range (min … max):    30.7 ms …  42.7 ms    92 runs
 
  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.
 
Summary
  /Users/shunsukesuzuki/.local/share/aquaproj-aqua/bin/aqua which mkghtag ran
    1.80 ± 0.18 times faster than /Users/shunsukesuzuki/go/bin/aqua which mkghtag