ledger-tool: make read_only consistent across bigtable subcommands

[CriesofCarrots]

Problem

LedgerStorageConfig contains a read_only field, but this isn't being populated correctly for some solana-ledger-tool bigtable subcommands. This could be a footgun for the CLI if someone modified solana-storage-bigtable methods to mutate the bigtable without handling appropriately in solana-ledger-tool.

Summary of Changes

Set more subcommands as read-only

I did confirm the setting works as intended, and prevents a block upload when set. However, the CLI just hangs indefinitely on Preparing the next 1 blocks for upload, which isn't very clear. I'll look at making that error out properly.

[steviez]

I searched the file for:

read_only: false

There are 7 current instances in master.

• upload needs r/w
• copy needs r/w for the target db

Of the remaining 5, 4 of them are already changed in this PR. The 5th instance is one I added another comment to, so once we land on the correct setting for that instance, I think we'll have all occurrences accounted for

[CriesofCarrots]

• copy needs r/w for the target db

Incidentally, I was delighted to discover that the two read_only settings in copy() were being handled correctly :)

[codecov]

Codecov Report

Merging #34513 (1431016) into master (65e10ae) will decrease coverage by 0.1%.
Report is 6 commits behind head on master.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #34513     +/-   ##
=========================================
- Coverage    81.8%    81.8%   -0.1%     
=========================================
  Files         820      820             
  Lines      220869   220869             
=========================================
- Hits       180791   180785      -6     
- Misses      40078    40084      +6     

[steviez]

LGTM