feat: simplify policy identification by using name as primary identif…

[Aliexe-code]

Summary
This PR removes the auto-generated UUID ID field from SPIKE policies and uses the user-provided name as the sole unique identifier, aligning with HashiCorp Vault's approach for better UX and simplicity.

Problem
SPIKE policies had two identifiers:

• ID: Auto-generated UUID (e.g., 550e8400-e29b-41d4-a716-446655440000)
• name: User-provided name (e.g., database-policy)

Testing

• All existing tests pass

• Build succeeds

• No breaking changes to existing behavior (IDs are internal only)

• This change is backward compatible for end users since they always used name in CLI commands. The ID field was only used internally and never exposed to users in the API responses of these endpoints.
  Follow-up Required ⚠️

SDK Dependency: The spike-sdk-go package contains request/response structs that still use ID fields. This PR includes a temporary workaround using the SDK's ID field but treating it as the policy name. A follow-up PR to the SDK is needed to:

• Rename PolicyReadRequest.ID to PolicyReadRequest.Name

• Rename PolicyDeleteRequest.ID to PolicyDeleteRequest.Name

• Update PolicyListItem.ID to be consistent

• issue Simplify policy identification: use name as primary identifier; remove ID from policies #250

[v0lkan]

Hey @Aliexe-code ; just saw this; will check it out and get back.

[v0lkan]

Quick update:

Overall, it makes sense.

But I have thoughts about

maybe removing policy ids altogether (name in itself uniquely identifies the policy anyway)

an autogenerated ID "can" be helpful; but I'm still not sure.

I'm adding this issue to my current radar to think about it further.

I'll update here.

[Aliexe-code]

Hey @v0lkan - sounds good, Let me know if you want me to make any changes, or if you'd prefer to remove the ID field entirely. Happy to adjust based on your preference.