Update config.json

Enabled initializing the model as a TokenClassification or SequenceClassification model for use in a downstream task.

Now using

```
model = AutoModelForTokenClassification.from_pretrained(model, trust_remote_code=True)
```
or

```
model = AutoModelForSequenceClassification.from_pretrained(model, trust_remote_code=True)
```
works, as it does for the NT-V1 models.

Was this functionality left out intentionally? I have tested this change with a fine-tuning Token Classification task with LoRa and seems to work fine.
If this change is desired, it should be integrated in all other NT-V2 models.



@hdallatorre

config.json

@@ -1,12 +1,16 @@
 {
   "add_bias_fnn": false,
   "architectures": [
-    "EsmForMaskedLM"
+    "EsmForMaskedLM",
+    "EsmForTokenClassification",
+    "EsmForSequenceClassification"
   ],
   "attention_probs_dropout_prob": 0.0,
   "auto_map": {
     "AutoConfig": "esm_config.EsmConfig",
-    "AutoModelForMaskedLM": "modeling_esm.EsmForMaskedLM"
+    "AutoModelForMaskedLM": "modeling_esm.EsmForMaskedLM",
+    "AutoModelForTokenClassification": "modeling_esm.EsmForTokenClassification",
+    "AutoModelForSequenceClassification": "modeling_esm.EsmForSequenceClassification"
   },
   "emb_layer_norm_before": false,
   "esmfold_config": null,