Add support for the Pact smart contract language

[emilypi]

This PR adds an entry for the Pact smart contract language.

Description

Following the directions in CONTRIBUTORS.md, this PR adds:

• A language entry for Pact
• An EBNF specification for Pact
• Sample scripts used in real world applications
• Sample licenses used in real world scripts

Checklist:

• I am adding a new language.
  • The extension of the new language is used in hundreds of repositories on GitHub.com.
    • Search results for each extension:
      • https://github.com/search?q=extension%3Apact+NOT+nothack&type=Code

NB: we have many private clients that do not open source their code, but store their scripts on private enterprise github accounts, outnumbering the number of representative public samples.

• I have included a real-world usage sample for all extensions added in this PR:

  • Sample source(s):

    • https://github.com/kadena-io/chainweb-node/blob/master/pact/coin-contract/v3/coin-v3.pact
    • https://github.com/kadena-io/chainweb-node/blob/master/pact/coin-contract/v3/coin-v3.repl
    • https://github.com/kadena-io/pact-examples
    • https://github.com/wrappedfi/wrapped_token_pact/blob/main/wrapped-token-v1.pact

  • Sample license(s):

    • https://github.com/kadena-io/pact/blob/master/LICENSE
    • https://github.com/kadena-io/pact-lang-api/blob/master/LICENSE

• I have included a syntax highlighting grammar: https://github.com/kadena-io/pact-atom/blob/master/grammars/pact.cson

• I have updated the heuristics to distinguish my language from others using the same extension.

[MrMrManatee]

I support this request as the Kadena blockchain continues to scale its operations to the masses!

[yasinsil]

Can you please check this ?

[lildude]

Please add samples for the .repl ext or remove it from this PR.

As an aside, usage is still too low to be accepted right now.

[emilypi]

@lildude updated with .repl sample script. Has the popularity window for support been shifted? It would seem like we have enough content for support at this point.

[emilypi]

@itsthejoker is there a problem you'd like to vocalize?

[lildude]

Usage has indeed improved from a quick glance so we might be good to go when it comes to merging.

[emilypi]

@lildude Addressed your comments. Anything else you need from me?

[emilypi]

Ping!

[lildude]

Pong! 🏓

"Patience, my young Padawan". The speed of review isn't going to change the rate at which this PR will be merged as PRs are only merged close to making releases.

[lildude]

Looks good now but the language is still too low in popularity. I'll review this again around each release and will only approve the PR once the popularity requirement has been met.

[emilypi]

Alright, thanks for the update on policy so i can stop pinging 😅. We'll see if we can get more people to publish their work openly.

Concerns have now been addressed. Now we wait for popularity to increase.

[emilypi]

We've had quite a bit of dev work come online recently. Have we met the bar yet @lildude?