feat: create a project for a user on signup as well as an org

[mattdjenkinson]

As part of datum-cloud/enhancements#602 we want to create a default project for new users on signup.

[scotwells]

Couple minor things!

[scotwells]

Do we show both the Description and the Display Name in the staff portal when listing projects? If we don't, we'll just see a big list of projects with the same display name.

[mattdjenkinson]

Good shout, i didn't think of that. We only show the Display name and Name atm but i can update the staff-portal to show both?

[scotwells]

That could work

[mattdjenkinson]

We could probably do with adding a user column to that table as well to make it even easier to see the customer details quickly.

[scotwells]

I think the description would work. Getting the user into that view doesn't make much sense because there's no single owner of a project and this table needs to support projects associated with single-user organizations and standard organizations.

[scotwells]

Implementation Guidance: Fix Personal Project Creation

The webhook error occurs because Milo's mproject.datum.net webhook expects parent context in UserInfo.Extra fields that controller-initiated requests don't have.

Solution: Client Impersonation with Extra Fields

Milo already has a pattern for this in user_webhook.go#L186-L208. Apply the same approach:

impersonatedConfig := rest.CopyConfig(r.RestConfig)
impersonatedConfig.Impersonate = rest.ImpersonationConfig{
    Extra: map[string][]string{
        "iam.miloapis.com/parent-name":      {org.Name},
        "iam.miloapis.com/parent-type":      {"Organization"},
        "iam.miloapis.com/parent-api-group": {"resourcemanager.miloapis.com"},
    },
}

impersonatedClient, err := client.New(impersonatedConfig, client.Options{Scheme: r.Scheme})
// Use impersonatedClient.Create() for project creation

The controller needs access to *rest.Config and RBAC permissions for impersonation with Extra fields.

See: project_webhook.go#L63-L71 for where validation fails.