[STORY-2698] feat(db-ng): Use new DatabaseNG from go-scalingo

[baptmaury]

Related to [STORY-2698]

Depends on Scalingo/go-scalingo#441

This PR remove the usage of App and Addon returned from api database endpoint. The DatabaseNG type has been updated. There is no new feature

• Add a changelog entry in the section "To Be Released" of CHANGELOG.md
• [STORY-2698] feat(db-ng): Remove usage of App and Addon from Databases api endpoint go-scalingo#441 is merged
• a new version of go-scalingo is released (containing [STORY-2698] feat(db-ng): Remove usage of App and Addon from Databases api endpoint go-scalingo#441)
• go.mod updated to use new release of go-scalingo.

[semgrep-code-scalingo]

Legal Risk

The following dependencies were released under a license that
has been flagged by your organization for consideration.

Recommendation

While merging is not directly blocked, it's best to pause and consider what it means to use this license before continuing. If you are unsure, reach out to your security team or Semgrep admin to address this issue.

MPL-2.0

• github.com/cyphar/filepath-securejoin 0.6.1

[notion-workspace]

🗒️ [FEAT][IST] Step-2.b Make usage of database object instead of app+addon

[matthieu526-scalingo]

I know this PR is not ready to be merged yet, as the SDK is not released. Nonethess, something weird happened. You updated a vendor file without impacting the go.mod.
What you can do to open a PR that is "clean" even if not definitive.

go get -u github.com/Scalingo/go-scalingo/v8@feat/db-ng/use-database-object-from-api
go mod tidy
go mod vendor

I think that would work 🙂

[curzolapierre]

Could you add an example in the PR's description please?

[baptmaury]

Did a last QA session:

• databases : ok
• database-info : ok
• database-create : there is an issue with the response message: -----> Your database ('') is being provisioned…

io.Statusf("Your %s database %s ('%s') is being provisioned…\n\n",
	db.Technology,
	db.ID,
	db.Name,
)

db seems empty but the db is created

• database-delete : ok