feat: Add MsgRegisterService to handle service registration

The commit message for these changes would be:

feat: Add MsgRegisterService to handle service registration

This commit adds a new message type `MsgRegisterService` to the DID module's transaction proto file. This message allows users to register a new service with a given permission scope and origin URI. The domain must have a valid TXT record containing the public key.

The changes include:

- Adding the `MsgRegisterService` message type with fields for authority, origin URI, and scopes
- Adding the `MsgRegisterServiceResponse` message type to handle the response
- Updating the Msg service to include a new `RegisterService` RPC method
- Implementing the `RegisterService` method in the keeper

This feature allows users to register new services on the DID chain, which is an important part of the overall DID functionality.

proto/did/v1/state.proto

@@ -5,6 +5,7 @@ option go_package = "github.com/onsonr/hway/x/did/types";
 
 import "cosmos/orm/v1/orm.proto";
 import "did/v1/genesis.proto";
+import "did/v1/enums.proto";
 
 // Aliases represents the `alsoKnownAs` property associated with a DID Controller
 message Aliases {
@@ -146,9 +147,15 @@ message Service {
   // The type of the service
   string service_type = 2;
 
-  // The service endpoint
-  string service_endpoint = 3;
-
   // The controller DID of the service
-  string controller_did = 4;
+  string controller_did = 3;
+
+  // The domain name of the service
+  string origin_uri = 4;
+
+  // The service endpoint
+  map<string, string> service_endpoints = 5;
+
+  // Scopes is the Authorization Grants of the service
+  repeated PermissionScope scopes = 6;
 }