[Bug] graphman accepts deployment or namespace misleading to errors

Bug report

In graphman help, like graphman drop --help it accepts the DEPLOYMENT as an identifier to which SG to remove. The Deployment is unique everywhere in our system and if I try to drop a SG by using the deployment it will get removed from everywhere as usual.

The problem is that the drop command also accepts the namespace, which is unique only to the respective shard where this SG is deployed.

The graphman shouldn't accept the namespace if the help is saying to use the deployment identifier, otherwise it leads to critical mistakes when we want to remove the SG only from a specific shard and not from everywhere.

Also if you might consider this also as a feature request, there should be a possibility to drop the SG only from a specific shard by using it's namespace (if it's a single SG in that table, otherwise throw a warning that's not possible to remove it because there are multiple deployments using the same table)

Relevant log output

No response

IPFS hash

No response

Subgraph name or link to explorer

No response

Some information to help us out

• Tick this box if this bug is caused by a regression found in the latest release.
• Tick this box if this bug is specific to the hosted service.
• I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

macOS

Beginne beim graphman-Einstiegspunkt drop --help und verfolge, wie seine Deployment-Kennung aufgelöst wird, wenn ein namespace angegeben ist. Bestätige das aktuelle Verhalten über Shards hinweg und definiere den Abschluss so, dass verhindert wird, dass namespace-Werte als Deployment-Kennungen akzeptiert werden; kläre dabei, ob das shardspezifische Entfernen im Umfang liegt. Im Issue wird kein Datei- oder Testpfad genannt.