refactor(wit): Rename ip.allocate to allocate-unsafe

Author: tomasol

README.md

@@ -59,7 +59,7 @@ obelisk client execution submit -f obelisk-flyio:activity-fly-http/ips@1.0.0-bet
 ```
 Allocate an IP:
 ```sh
-IP=$(obelisk client execution submit -f --json obelisk-flyio:activity-fly-http/ips@1.0.0-beta.allocate -- \
+IP=$(obelisk client execution submit -f --json obelisk-flyio:activity-fly-http/ips@1.0.0-beta.allocate-unsafe -- \
 \"$FLY_APP_NAME\" '{ "config":{ "ipv6": {"region": null} } }' | jq -r '.[-1].ok' )
 ```
 Release an IP:

activity/fly-http/impl/src/ips.rs

@@ -172,7 +172,10 @@ where
 }
 
 impl ips::Guest for crate::Component {
-    fn allocate(app_name: String, request: ips::IpRequest) -> Result<ips::IpAddress, String> {
+    fn allocate_unsafe(
+        app_name: String,
+        request: ips::IpRequest,
+    ) -> Result<ips::IpAddress, String> {
         (|| {
             let app_name = AppName::new(app_name)?;
             block_on(allocate_ip(app_name, request))

activity/fly-http/wit/obelisk-flyio_activity-fly-http@1.0.0-beta/fly.wit

@@ -54,10 +54,10 @@ interface ips {
         ip-variant: ip-variant,
     }
 
-    /// Allocate an IP address
-    /// Idempotency note: Retry of a success will allocate another IP address.
+    /// Allocate an IP address.
+    /// Non idempotent: Retry of a success will allocate another IP address.
     /// Upon allocating an IP the caller should use `list` and `release` to prevent this issue.
-    allocate: func(app-name: string, request: ip-request) -> result<ip-address, string>;
+    allocate-unsafe: func(app-name: string, request: ip-request) -> result<ip-address, string>;
 
     /// List allocated IP addresses
     %list: func(app-name: string) -> result<list<ip-detail>, string>;