Legacy proposal changes

[lukebp]

I'm just about done with the final round of testing for decred/politeia#1632. Now that the legacy proposals will be included in the tstore backend and returned from the API like any other proposal, we'll need to differentiate between legacy git proposals and normal tstore proposals in the gui.

The gui can tell that a proposal is a legacy proposal by inspecting the legacytoken field of the proposalmetadata.json proposal file. This field will be populated with the git repo token for the proposal if the proposal is a legacy proposal. This is the only place in the proposal data that will reference the proposal's git token. All other token fields will reference the proposal's tstore token. These are not the same. The tstore token is created during the import process and matches the token format of the other tstore proposals.

The gui changes that I was thinking should be made include:

1. Have some kind of indicator that tells the user that this is a legacy proposal and explain what that means.

2. One of the downsides of importing the legacy proposals into the tstore backend was that it breaks the proposal signatures. For this reason, all of the signature fields have been left empty. The git repo will serve as the source of truth for the original legacy proposal data and their sigantures, so we'll want to provide a link in the gui to this data.

Please let me know if you encounter any issues or find anything that looks off with the legacy proposals. I've done quite a bit of testing and I think I've squashed all of the bugs, but a second set of eyes never hurts.

Importing legacy data locally

The full import process takes 7.5 hours, so I've put together a script that you can run that only imports a handful of the legacy proposals. This should be run in the same directory as the mainnet git repo after you've installed the legacypoliteia CLI tool. You do not need to have politeiad or politeiawww running. You do need to have the tlog server, tlog signer, and MySQL database running.

Once the data has been imported, politeiad must be reset using the --fsck flag so that the caches are rebuilt to include the newly imported data.

Note, this is mainnet data and will be imported into the mainnet databases. Make sure you are running politeiad and politeiawww against mainnet, not testnet, when you turn them on.

#!/usr/bin/env sh

convertCmd='legacypoliteia convert mainnet --overwrite'
importCmd='legacypoliteia import legacy-politeia-data --stubusers'

# Approved proposal
${convertCmd} \
  --token=95a14094485c92ed3f578b650bd76c5f8c3fd6392650c16bd4ae37e6167c040d

# Rejected proposal
${convertCmd} \
  --token=350f64b09cc3d2dbae453f49177ca70505ba701fb141a8fc446698460fd5e221

# Abandoned proposal
${convertCmd} \
  --token=8a0932475eba2139df82f885fbdff9845e98551b47c44c378bf51840ae616334

# RFP parent
${convertCmd} \
  --token=91beceac460d9b790a01fb2e537320820bab66babfeb5eb49a022ea5952b5d73

# RFP submissions
${convertCmd} \
  --token=02d9fc23d20017503a615459e2e0c7b333660bd5e44cde7f2c40db2ebeb986bd
${convertCmd} \
  --token=45323975f533d2c07db33b06dc3e2af5e1c452eb1a68abffb8296aace53ec9a6
${convertCmd} \
  --token=f0a00d5f7598251820e8ab5bdc184adba980e404216124da91538625ac7c4e0a
${convertCmd} \
  --token=d6ff458cf0dcfed1d45f5a93af2a681ef220732f07a09fb4de934ada928bf1b3

# Proposal with duplicate comments
${convertCmd} \
  --token=2ef74fa5f0b558442cb85b1235c8c551a51ff5d8b8de44dead48b8b59c8fc1de

# Import the converted data
${importCmd}