/claim #2

Added persisted credential handling: new credential struct + YAML load/save under OS default path; user-only perms.

Client construction now pulls stored endpoint/token/cert, infers TLS, loads key pairs when provided, and attaches bearer auth via per-RPC creds.

Configure flow now pre-fills from stored creds, prompts for token/cert, validates cert/key pairing, persists credentials before creating the client, and fails fast on client creation errors.

• Files touched: added [credentials_storage.go]; updated [grpc.go]; updated [configure.go].

• Credentials persistence: new YAML-backed store at [~/.permify/credentials], user-only perms, fields for endpoint/token/cert path/cert key.

• Client init: [New] now pulls stored creds when endpoint is empty, infers TLS (https/grpcs or cert presence), loads keypair when provided, and applies bearer auth via per-RPC creds (secure vs. insecure paths).

• Configure flow: prompts pre-filled from stored creds, captures token/cert paths, enforces cert+key pairing, writes credentials before client creation, and surfaces client creation errors early.

To test, run: go run ./cmd/permctl configure

In the video, it showed error because those were not real data. you can see that it return previous api url i entered. Try it will real data, it will show success.

here is the video: https://youtu.be/YiGxpxr3-xA