[W-21836474] fix(soql): .soql files are automatically detected as language SOQL, not Apex

[daphne-sfdc]

What does this PR do?

In the Apex extension's package.json, we had this:

"languages": [
      {
        "id": "apex",
        "aliases": [
          "Apex",
          "apex"
        ],
        "extensions": [
          ".cls",
          ".trigger",
          ".soql"
        ],

And in the SOQL extension's **package.json, we had this:

    "languages": [
      {
        "id": "soql",
        "aliases": [
          "soql",
          "SOQL"
        ],
        "extensions": [
          ".soql"
        ]
      }
    ],

This meant .soql files can be claimed as either language Apex or language SOQL, depending on which extension is activated first. In Windows, the Apex extension is activated before the SOQL extension, so .soql files are incorrectly claimed as language Apex.

As you can see, .soql files with language Apex do not have the "Run Query" and "Get Query Plan" code lens.

What issues does this PR fix or reference?

@W-21836474@

[daphne-sfdc]

@peternhale Changes in the SOQL extension reverted, since for future installs the Apex extension will no longer claim .soql files, leaving them for the SOQL extension.