I245 add suport for forceful project deletion

[MaheshPunjabi]

What was changed?
from #245

• api: projects_force_delete
  Add an API extension string for this in doc/api-extensions.md and internal/version/api.go. call it "projects_force_delete"

---

Work-In-Progress:

• Update the projectDelete API handler,in "cmd/incusd/api_project.go" to handle the force variable and if set to true, then go through everything the project owns and delete it. You probably want to start with instances, then volumes and buckets, then profiles, then networks (starting with acls, zones, peering before networks themselves).

• Re-generate the swagger YAML data (make update-api).

• Add a DeleteProjectForce function to "client/incus_projects.go" which passes a ?force=true to the API. add that function to the ImageServer interface.

• Add new "force" argument to "cmd/incus/project.go". when passed, call DeleteProjectForce

• Re-generate the translation template for the new CLI string.

---

Tests:
gofmt -d passed(for api.go)
make completed fine

[stgraber]

@MaheshPunjabi how's this going? Need any help?

[MaheshPunjabi]

@MaheshPunjabi how's this going? Need any help?
@stgraber Yes, thank you. I've posted a couple of questions on line 1570, 71 and 91.
Also, I'm still trying to figure out the step "Empty the default profile" . Should I just call projectCreateDefaultProfile ?

[stgraber]

Ah, in the future please use messages in the PR directly or use Github's in-line comment feature as we don't normally review the code within draft PRs so will not notice code comments like the ones you've left.

[MaheshPunjabi]

@stgraber Can you take a quick look at the changes in recent commits to see if they look good? I'm doubtful on the "Empty the default profile" part.

[stgraber]

I think the DB code to empty the default profile should work. That said, I don't think it's a good idea to directly poke the database as in many other cases (networks, storage, instance, ...) there is more to Incus than just some DB records and this will not properly clean things.

A more reliable approach would be to use our own Go API to perform those actions, effectively acting as if the incus command line tool was issuing those commands.

Basically doing something like:

s, err := incus.ConnectIncusUnix("", nil)
if err != nil {
    return err
}

And then using s to call things like DeleteInstance, DeleteProfile, UpdateProfile (to empty the default profile, DeleteStoragePoolVolume, DeleteStoragePoolBucket`, ...

You can compute the actual list of stuff to delete based on a GetProject call and looking at the UsedBy field. This also makes it possible to immediately fail if there are things in UsedBy that the function doesn't yet know how to delete (future proofing).

[stgraber]

Going to take this one and the work done in #850 to get something we can merge in 6.2.