TC: support non-literal defconst values and fix generated Infos for consts

[sirlensalot]

As seen in #1105 , but the actual bug driving the change is still open:

pact> (verify 'coin)
<interactive>:1:0: : Native in value context: ["0" "1" "2" "3" "4" "5" "6" "7" "8" "9" "10" "11" "12" "13" "14" "15" "16" "17" "18" "19"]

It's hard to track this down because there is no Info on the term; this is because the offending code --

  (defconst VALID_CHAIN_IDS (map (int-to-str 10) (enumerate 0 19))
    "List of all valid Chainweb chain ids")

-- populates the value from applying a native at module load. Generally runtime-generated values do not have code locations, but in the defconst case it would be useful to supply them perhaps by overwriting the Info value with the old code location.

The actual bug is the typechecker cannot handle non-literals in consts since these are Direct ref values. To fix either specifically handle lists, or investigate whether to just recurse back to toAST and stop the special-casing for Direct.

[sirlensalot]

Indeed if we replace (map ... enumerate ...) with the literal ["0" ... "19"] the output becomes:

*** Exception: ../chainweb/pact/coin-contract/v5/coin-v5.pact:160:28: Native in value context: ["0" "1" "2" "3" "4" "5" "6" "7" "8" "9" "10" "11" "12" "13" "14" "15" "16" "17" "18" "19"]