fix(secrets): default delete --type to shared, matching set

[solomonerous]

Fixes Infisical/infisical#7805

infisical secrets set and infisical secrets get default to --type shared, but infisical secrets delete defaults to --type personal. So the obvious flow - set a secret, then delete it - always fails with a 404 "Secret not found" unless you remember to pass --type shared, and the error gives no hint that the type is the problem.

This flips the delete default to util.SECRET_TYPE_SHARED so it matches the rest of the group, and drops the manual "(default: personal)" suffix in the flag help since cobra prints the actual default anyway.

Builds clean (go build ./packages/cmd/); go vet only reports the four pre-existing run.go format-string warnings that are already on main.

If maintainers would rather not change the default, two alternatives I'm happy to implement instead: fall back to shared when the personal lookup 404s, or keep the defaults and just make the 404 message mention --type.

[greptile-apps]

Greptile Summary

This PR changes infisical secrets delete to default --type to shared, aligning it with the default used by secrets set, and removes the stale manually written default from the flag description.

• Uses the existing util.SECRET_TYPE_SHARED constant as the Cobra flag default.
• Allows Cobra to render the effective default in command help.

Confidence Score: 5/5

The PR appears safe to merge because the changed default is transmitted correctly and remains overridable with an explicit --type.

The shared constant resolves to the API-supported "shared" value, and omitted and explicit --type shared invocations follow the same existing delete request path without introducing a blocking failure.

Important Files Changed

Filename	Overview
packages/cmd/secrets.go	The delete command now sends type: "shared" when --type is omitted; explicit personal and shared selections remain available, and no actionable defect was found.

_{Reviews (1): Last reviewed commit: "fix(secrets): default delete --type to s..." | Re-trigger Greptile}

[rmdly]

Heads up that this overlaps with #375, which I opened on 26 August with the same change to secrets.go. No issue from my side over which one lands, just flagging it so a reviewer sees both rather than merging one and closing the other unaware.

The one difference is that #375 also adds TestSecretsTypeFlagDefaults in packages/cmd/secrets_test.go, asserting that secretsSetCmd and secretsDeleteCmd agree on the --type default so the two cannot silently drift apart again. If this PR is the one you would rather take, I am happy to send that test separately on top of it.