Updating Project Resource to have "is_default" configurable

[danaelhe]

(murked my previous PR #849 bc got into a hairy merge issue)

Per #848.

@yordis had a great suggestion for allowing to provision digitalocean_project resource as "Default Project". Making "is_default" configurable. This means:

• You can initialize a new project to be the default.
• You can’t edit a project to no longer be default (400 (request "acb5906e-bf48-49e3") you must always have a default project) even if you have other projects, it won’t automatically assign another project to be default
• You can’t delete a project that is the default (^^)
• You must first assign another project to be default first before you can delete the old default project

[danaelhe]

seems like the acceptance test for this pr passed (TestAccDigitalOceanProject_CreateWithIsDefault) but a few others did not?

[scotchneat]

@danaelhe We're having issues with the acceptance tests and need to redesign the approach. So those are non-blocking right now.

[scotchneat]

Looks great! 👍🏽

[andrewsomething]

For future reference, this is how to edit is_default on a project without hitting an error. Starting from a config like:

resource "digitalocean_project" "default" {
  name = "test-default"
  is_default = true
}

resource "digitalocean_project" "not-default" {
  name = "test-not-default"
}

You can switch the default by adding an explicit dependency to ensure the second project is set to default before updating the first. E.g.

resource "digitalocean_project" "default" {
  name = "test-default"
  depends_on = [
    digitalocean_project.not-default
  ]
}

resource "digitalocean_project" "not-default" {
  name = "test-not-default"
  is_default = true
}

[andrewsomething]

👍 LGTM!