Tunnel is configured with incorrect IP address

[danielsharvey]

The tunnel is configured with the incorrect IP address.

The value bastion.publicIp is referenced rather then the Elastic IP address(es).

The Pulumi docs state:

Public IP address assigned to the instance, if applicable. 
**NOTE**: If you are using an `aws.ec2.Eip` with your instance, you should 
refer to the EIP's address directly and not use `publicIp` as this field will 
change after the EIP is attached.

This results in the tunnel forwarding to the wrong IP address and does not work.

This seems to be experienced by others e.g. #5657.

The relevant code is:

sst/platform/src/components/aws/vpc.ts

Lines 679 to 700 in e4159bb

	function registerOutputs() {
	self.registerOutputs({
	_tunnel: all([
	self.bastionInstance,
	self.privateKeyValue,
	self._privateSubnets,
	self._publicSubnets,
	]).apply(
	([bastion, privateKeyValue, privateSubnets, publicSubnets]) => {
	if (!bastion) return;
	return {
	ip: bastion.publicIp,
	username: "ec2-user",
	privateKey: privateKeyValue!,
	subnets: [...privateSubnets, ...publicSubnets].map(
	(s) => s.cidrBlock,
	),
	};
	},
	),
	});
	}