Fixed rename by using put instead of post

[cloutiertyler]

Description of Changes

Closes #2763

API and ABI breaking changes

Technically a breaking change because it changes the behavior of the CLI, but it's arguably a bug fix.

Expected complexity level and risk

2 because of the breaking nature

Testing

• Test that you can rename a database (I have not done this yet)
  • Confirmed that old db name no longer existed after renaming
• Existing name-setting smoketest passes

[bfops]

@cloutiertyler I updated the code meaningfully, as well as augmenting the smoketest. The new endpoint just returns a string that's either "Success" or an error message, so I've removed all the code that tries to parse a well-typed error out of the response.

[bfops]

(status here: the smoketests have uncovered that the PUT version of the request will happily clobber existing names without emitting an error)

[bfops]

To clarify, you cannot clobber a database that you do not own:

$ cargo run -pspacetimedb-cli -- rename --to rename-test-module rename-from-module
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.35s
     Running `target/debug/spacetimedb-cli rename --to rename-test-module rename-from-module`
Error: Error: {"PermissionDenied":{"domain":"rename-test-module"}}

[jdetter]

I am approving but I made some of the changes so @bfops should take a look as well before merging.

[bfops]

LGTM. Idk why I had to change it to parse a non-JSON response at one point, but it does seem to consistently return JSON responses now, so.. 🤷