test: Fix skipped List component test

[DafyddLlyr]

What's the problem?

• There was a skipped test introduced in fix: List should record val, not text, in passport and calculate total units by development type when applicable #3263
• This was failing when un-skipped, as react-testing-library was unable to locate DOM elements to interact with

What's the solution?

Variables need be be reinstated when a new list item is added, otherwise they hold onto their old references and are invalid.

[DafyddLlyr]

This may look like I'm "fixing" the expected output to make the test pass, but in this instance it's actually an incorrect payload.

This now matches the other (already passing) test example here -

planx-new/editor.planx.uk/src/@planx/components/List/utils.test.ts

Lines 73 to 74 in be6a176

	"proposal.units.residential.total.units.development.newBuild": 3,
	"proposal.units.residential.total.units.development.changeOfUseTo": 2,

And we can see that development is added to the path here -

planx-new/editor.planx.uk/src/@planx/components/List/utils.ts

Lines 68 to 72 in be6a176

	Object.entries(baseSums).forEach(([k, v]) => {
	if (v > 0) {
	formattedSums[`${fn}.total.units.development.${k}`] = v;
	}
	});

[github-actions]

Removed vultr server and associated DNS entries

[RODO94]

Changes look good to me and relates well to the PR description.