review/refactoring of JSON (config) files

even with errors like #16 fixed, the JSON files would be ideally cleaned-up (as in let's do not drag this around if we do not need it):

mbohun@linux-cr70:~/src/nsl-infra.git> cat ./shard_vars/icvcn.json | jq -S

{
  "banner_text": "Viruses",
  "description_html": "<p>This section of the National ex-Australia Species List infrastructure delivers names and taxonomies for organisms named according to the {{shard_name_full}}. The data comprise names, bibliographic information, and taxonomic concepts for organisms that are neither native to nor naturalised in Australia. The {{shard_namespace_full}} ({{ shard_namespace_UPPER }}) provides names and bibliographic information. The {{tree_banner_text}} ({{ taxonomy_name }}) provides a provisional taxonomy.</p>",
  "menu_label": "Biosecurity {{target_kingdom_ccase}}",
  "services_path_tree_element": "bvc",
  "shard_data_load_file": "data_load_virus.sql",
  "shard_images": {
    "filename-00": "bvni-banner.png",
    "filename-01": "bvni-vert-200.png"
  },
  "shard_name": "icvcn",
  "shard_name_caps": "ICVCN",
  "shard_name_full": "International Code of Virus Classification and Nomenclature",
  "shard_namespace": "bvni",
  "shard_namespace_UPPER": "BVNI",
  "shard_namespace_UPPER_description": "The {{ shard_namespace_full }} ({{ shard_namespace_UPPER }}) is a tool for the biosecurity community that deals with {{target_kingdom}} names and their usage in the scientific literature, whether as a current name or synonym, for {{shard_name_caps}}-named organisms that are NOT native to, or naturalised in Australia. {{shard_namespace_UPPER}} does not recommend any particular taxonomy or nomenclature. For a listing of currently accepted scientific names for ex-Australia{{target_kingdom_plural_more}}or {{target_kingdom_plural}}, please use {{tree_banner_text}} ({{taxonomy_name}}) link above.",
  "shard_namespace_full": "Biosecurity {{target_kingdom_ccase}} Name Index",
  "shard_nsl_ddl_file": "icn-ddl.sql",
  "target_kingdom": "virus",
  "target_kingdom_ccase": "Virus",
  "target_kingdom_ccase_caps": "Viruses",
  "target_kingdom_plural": "virus",
  "target_kingdom_plural_more": "",
  "taxonomy_message": "The {{tree_banner_text}} ({{taxonomy_name}}) is a working taxonomy for the species that have been referenced in a biosecurity context in Australia",
  "taxonomy_name": "BVC",
  "taxonomy_name_description": "The {{tree_banner_text}} ({{ taxonomy_name }}) is a working taxonomy for use by biosecurity specialists in Australia.",
  "tree_banner_text": "Biosecurity {{target_kingdom_ccase}} Checklist",
  "tree_label_text": "{{ tree_banner_text }}"
}

NOTES:

the overall structure resembles more a .properties file than JSON

"shard_data_load_file": "data_load_virus.sql",
"shard_images": {
"filename-00": "bvni-banner.png",
"filename-01": "bvni-vert-200.png"
},
"shard_name": "icvcn",
"shard_name_caps": "ICVCN",
"shard_name_full": "International Code of Virus Classification and Nomenclature",
"shard_namespace": "bvni",
"shard_namespace_UPPER": "BVNI",
"shard_namespace_UPPER_description": "The {{ shard_namespace_full }} ({{ shard_namespace_UPPER }}) is a tool for the biosecurity community that deals with {{target_kingdom}} names and their usage in the scientific literature, whether as a current name or synonym, for {{shard_name_caps}}-named organisms that are NOT native to, or naturalised in Australia. {{shard_namespace_UPPER}} does not recommend any particular taxonomy or nomenclature. For a listing of currently accepted scientific names for ex-Australia{{target_kingdom_plural_more}}or {{target_kingdom_plural}}, please use {{tree_banner_text}} ({{taxonomy_name}}) link above.",
"shard_namespace_full": "Biosecurity {{target_kingdom_ccase}} Name Index",
"shard_nsl_ddl_file": "icn-ddl.sql",

instead of something like, example:

"shard" : {
  "data_load_file": "data_load_virus.sql",
  "nsl_ddl_file": "icn-ddl.sql",
  "images": {
      "filename-00": "bvni-banner.png",
      "filename-01": "bvni-vert-200.png"
  },
  "name": { 
      "short" : "icvcn",
      "full": "International Code of Virus Classification and Nomenclature"
  },
  "namespace": {
      "name": "bvni",
      "description": "The {{ shard_namespace_full }} ..."
  }
}

do we REALLY need/want fields like:
```
{
  "shard_name": "icvcn",
  "shard_name_caps": "ICVCN",
  "shard_namespace": "bvni",
  "shard_namespace_UPPER": "BVNI"
}
```
Even if such JSON fields would be really required (as in you can't upper-case/lower-case/cammel-case) strings in the browser/js, you would simply generate such fields from a template as part of the build/installation (anything really - just to avoid keeping such field in sync manually).

ess-acppo / nsl-infra

review/refactoring of JSON (config) files #17