[Bug] the 'ALTER timeseries {ts} DROP {tag1 .. tagN}' clause is confusing (no tags/attributes discrimination)

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.

### Version

1.3 release

### Describe the bug and provide the minimal reproduce step

If a same name is used for TAGS and ATTRIBUTES, the DROP clause doesn't know to discriminate them.
```
ALTER timeseries root.turbine.d1.s1 ADD TAGS meta1=tag_value
ALTER timeseries root.turbine.d1.s1 ADD ATTRIBUTES meta1=attr_value
ALTER timeseries root.turbine.d1.s1 DROP meta1
ALTER timeseries root.turbine.d1.s1 DROP meta1
```

### What did you expect to see?

DROP should accept a TAGS/ATTRIBUTES specifier (as the others clauses, ADD/UPSERT)

### What did you see instead?

IoTDB seems to drop the TAGS at 1th call. The second call removes the attribute

### Anything else?

The SET or RENAME clauses exhibit same behavior

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Inizia riproducendo la sequenza ALTER timeseries dall’issue, inclusi TAGS e ATTRIBUTES con lo stesso nome e i relativi casi SET e RENAME. Traccia la gestione di ALTER timeseries per DROP, SET e RENAME, quindi aggiungi una copertura di regressione che dimostri che la selezione esplicita di TAGS o ATTRIBUTES rimuove solo i metadati richiesti.

Scritto dal modello di indicizzazione a partire dal testo della issue.