Potential Conflict with Generic Secret Path Name in ~/.secrets.json

[Jalalx]

The current secret path defined in the Harness CLI uses a very generic file name (~/.secrets.json), which has a potential risk of conflicting with other tools (or personal notes) that might use the same file name.

const SECRETS_STORE_PATH = ".secrets.json"

Is there a specific reason for choosing such a generic name for this file?

To reduce the risk of conflicts, it would be beneficial to store this file in a dedicated directory, such as ~/.harness/.secrets.json.

[Jalalx]

Seems to be duplicate of #37