Add grammar for Apex

[muenzpraeger]

Description

This PR changes the association of Salesforce's Apex language from source.java to source.apex. That includes a switch from using Java language definitions to the official tmLanguage definition here.

Checklist:

• I am associating a language with a new file extension.

  • The new extension is used in hundreds of repositories on github.com
    • Search results for each extension:
      • https://github.com/search?q=path%3A*.trigger+account+NOT+nothack&type=code
  • I have included a real-world usage sample for all extensions added in this PR:
    • Sample source(s):
      • https://github.com/trailheadapps/apex-recipes/blob/main/force-app/main/default/classes/Trigger%20Recipes/LogTriggerHandler.cls

• I am changing the source of a syntax highlighting grammar

  • Old: https://github.com/textmate/java.tmbundle
  • New: https://github.com/forcedotcom/apex-tmLanguage

[muenzpraeger]

Waiting for forcedotcom/apex-tmLanguage#54 to be merged.

[lildude]

I can see that you've manually updated files rather than following the instructions in the CONTRIBUTING.md file and using the supplied scripts. Please don't.

Please use the scripts provided in this repo to change the grammar source.

See my inline comments for the two extensions you're adding.

If in doubt, or for an easy life, don't add these extensions in this PR and leave it purely as a grammar source change PR. Users can implement an override for these files if they feel heavily wed to getting syntax highlighting.

[muenzpraeger]

@lildude Anything to change on my end for the tests?

[lildude]

Yup. The order of the submodules:

  1) Failure:
TestPedantic#test_submodules_are_sorted [/home/runner/work/linguist/linguist/test/test_pedantic.rb:68]:
Expected false to be truthy.

This stems from you manually doing things rather than using the scripts (the sorting happens at the end of the script/add-grammar script).

You can run script/sort-submodules and commit the updated .gitmodules file.

[muenzpraeger]

Got it. Weird, b/c I undid my changes and then ran the scripts. On it.

[lildude]

LGTM. Thanks.

Note: this PR will not be merged until close to when the next release is made. See here for more details.

[Arv18]

I understand that adding the extensions, like in an old pull request #4640 are now not necessary.
Thanks

[lildude]

@Arv18 If they meet our usage requirements, they can be added. You abandoned the last PR so it was closed (when we still used the stale bot). Feel free to open a new PR and be sure to follow the details in the CONTRIBUTING.md file and fill in the template. Keep in mind, like that last PR, the new PR will not be merged until the usage of the new extensions meets our usage requirements. Until then, you can use an override.