phylo: drop rule rename_and_ready_for_nextclade

[jameshadfield]

From #94 (comment)

Finally, there's one more "modify-the-dataset-JSON" script which comes after the strain-name switch: rule rename_and_ready_for_nextclade. This script drops the "genome_clade_annotation" coloring and transfers those node_attrs (if present) to be branch labels. This can be avoided by:

• Not exporting "genome_clade_annotation" as a coloring on the tree
• Creating an intermediate node-data JSON which defines "genome_clade_annotation" as branch labels rather than node_attrs.

Looks like genome_clade_annotation used to be added in as "custom" clade labels
Since the workflow has switched to using augur clades built-in options to define custom labels, I think it can be removed.

[joverlee521]

I'm not sure we can remove the entire rule since the rename_and_nextclade.py script is merging in the pathogen.json to make the build more "View in Nextclade" friendly. However, if we at least remove the genome_clade_annotation bits, maybe this can be modified to merge the pathogen.json and the auspice_config.json prior to export.