[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!

Comienza reproduciendo la secuencia de ALTER timeseries del issue, incluidos TAGS y ATTRIBUTES con el mismo nombre y los casos relacionados de SET y RENAME. Rastrea el procesamiento de ALTER timeseries para DROP, SET y RENAME, y añade después cobertura de regresión que demuestre que la selección explícita de TAGS o ATTRIBUTES elimina únicamente los metadatos solicitados.

Escrito por el modelo de indexación a partir del texto del issue.