🪲 Bug Report - AzureAvSetBasicPublicIPUpgrade: "Skipping upgrade" does not work due to "return" statement.

## Describe the bug
AzureAvSetBasicPublicIPUpgrade: "Skipping upgrade" does not work due to "return" statement.

## To Reproduce

Steps to reproduce the behavior:

1. Excute the script to the VM with no public IP address resource in given AvSet.
2. Logged: `[WARNING] VM '' does not have any public IP addresses attached. Skipping upgrade.`
4. Then Logged `[INFO] ####### Upgrade process complete. #######`. The other VMs which has public IP addresses are also skipped.

## Expected behavior
The VMs which has public IP addresses should be upgraded.
The VMs which has no public IP addresses should be skipped.

"return" statements in line 224 and 235 should be replaced in "continue" statements.

## Screenshots 📷

## Additional context - please include:

- Version of the AzureBasicLoadBalancerUpgrade module you are running (see: `Get-Module AzureBasicLoadBalancerUpgrade` after importing the module.): 1.0.0

- Version of PowerShell you are running (`$PSVersionTable`)

- The JSON View or template of the VMSS and Load Balancer(s) to be migrated
N/A

从 AzureAvSetBasicPublicIPUpgrade 模块中第 224 行和第 235 行附近开始，issue 在这里指出了 return 语句。使用一个没有 public IP 的 VM 和其他具有 public IP 的 VM 重现该情况；完成的标准是前者被跳过，而后者继续执行 upgrade 流程。

由索引模型根据 Issue 内容生成。