dms: allow "bundle destroy" regarding if configuration matches state

[denik]

Changes

"bundle destroy" will now always work. Other commands (plan/deploy) still error if state "deployment_history" feature does not match requested in config.

Why

It makes it easier if destroy always works and fixes our own clean up procedure which relies on destroy over fabricated config.

[eng-dev-ecosystem-bot]

Integration test report

Commit: ee1feee

Run: 35229536420

	Env	✅​pass	🙈​skip	Time
✅​	aws linux	280	16	4:29
✅​	aws windows	282	14	5:35
✅​	azure linux	279	16	4:10
✅​	azure windows	281	14	4:05
✅​	gcp linux	280	16	4:39
✅​	gcp windows	282	14	4:04

Top 3 slowest tests (at least 2 minutes):

duration	env	testname
5:11	aws windows	TestAccept
3:43	azure windows	TestAccept
3:40	gcp windows	TestAccept

[github-actions]

Approval status: pending

/acceptance/bundle/ - needs approval

6 files changed
Suggested: @shreyas-goenka
Also eligible: @janniklasrose, @pietern, @andrewnester, @lennartkats-db, @anton-107

/bundle/ - needs approval

4 files changed
Suggested: @shreyas-goenka
Also eligible: @janniklasrose, @pietern, @andrewnester, @lennartkats-db, @anton-107

/cmd/apps/ - needs approval

Files: cmd/apps/import.go
Suggested: @MarioCadenas
Also eligible: @fjakobs, @Shridhad, @atilafassina, @keugenek, @igrekun, @pkosiec, @pffigueiredo, @ditadi, @calvarjorge

/cmd/bundle/ - needs approval

6 files changed
Suggested: @shreyas-goenka
Also eligible: @janniklasrose, @pietern, @andrewnester, @lennartkats-db, @anton-107

_{Any maintainer (@andrewnester, @anton-107, @pietern, @shreyas-goenka, @simonfaltum, @renaudhartert-db, @janniklasrose, @lennartkats-db, @rugpanov, @rclarey) can approve all areas.
See OWNERS for ownership rules.}