feat:store additional data with permissions

[pavanjoshi914]

Describe the changes you have made in this PR

prototype to store nostr permssions in db.

looking over the designs and code i think we don't need to add additional data in the db for permissions and we can achieve it without such changes. as such changes will also need migrations.

1. we declare our permsision types in such enum, we can just add new permissions and change names of permssions according to which we want to display it in site preferences dialogue

export enum PermissionMethodNostr {
  NOSTR_SIGNMESSAGE = "nostr/signMessage",
  NOSTR_SIGNSCHNORR = "nostr/signSchnorr",
  // this can be nostr login
  NOSTR_GETPUBLICKEY = "nostr/getPublicKey",
  NOSTR_NIP04DECRYPT = "nostr/nip04decrypt",
  NOSTR_NIP04ENCRYPT = "nostr/nip04encrypt",
}

2. we store enabled property to true when we add permissions and set it to false when we revoke permissions so we don't need to store allow and deny as well we can use this variable and just change ui to use buttons which to allow or revoke a permissions

3. type definitions: type definitions are incomplete for event kinds we need to add type definitions

From the above explanation, i think we can achieve permission management without storing additional metadata. wdyt @reneaaron

[reneaaron]

Closing in favor of #3054