Bump packer azure plugin version to 2.3.0

[jenkins-infra-updatecli]

Bump packer azure plugin version

Update the azure plugin version in main.pkr.hcl

1 file(s) updated with "azure = {${1}version = \"2.3.0\"": * main.pkr.hcl

2.3.0

Release published on the 2025-02-24 19:14:27 +0000 UTC at the url https://github.com/hashicorp/packer-plugin-azure/releases/tag/v2.3.0

<!-- Release notes generated using configuration in .github/release.yml at v2.3.0 -->

## Breaking Changes

On March 31st 2025 Azure will block the creation of basic public IP addresses, prior to this version would still create basic sku public IP's which is when the field `private_virtual_network_with_public_ip` is set, which enables bringing your own virtual network and subnet, and having the plugin create a network interface and public IP to connect to the build virtual machine from the host machine. 

As of v2.3.0 a standard SKU Public IP Address will be created in Azure, however standard SKU Public IP's require a network security group to define any ingress, otherwise it is all blocked.  This means users will need to create a network security group to allow ingress to their virtual networks.

There is an open request to allow Packer to create a network security group for users this was opened before this change.  This can cause conflicts with the subnet's network security group, but since we expect that users may run into change, we will likely need to add support for Packer creating the NSG at a NIC level. If you have any feedback on how we address this problem, please reach out here https://github.com/hashicorp/packer-plugin-azure/issues/468 asap.

If you are using `private_virtual_network_with_public_ip`, you should upgrade to this release by March 31st 2025 or your builds will likely start failing.

 You can read more about this deprecation [in this official post from Microsoft](https://azure.microsoft.com/en-us/updates?id=upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired)

If you want to roll back to the previous behavior for this you can set the `public_ip_sku` field to Basic, but this will stop working on March 31st as stated above 

## What's Changed
### Other Changes
* Bump github.com/hashicorp/packer-plugin-sdk from 0.5.4 to 0.6.0 by @dependabot in https://github.com/hashicorp/packer-plugin-azure/pull/464
* Make it clearer where users can find a target_region example by @JenGoldstrich in https://github.com/hashicorp/packer-plugin-azure/pull/470
* Use Standard IP SKU by default for edge case with `private_virtual_network_with_public_ip` field by @JenGoldstrich in https://github.com/hashicorp/packer-plugin-azure/pull/469


**Full Changelog**: https://github.com/hashicorp/packer-plugin-azure/compare/v2.2.1...v2.3.0

Jenkins pipeline link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[smerle33]

was green no need to wait for a new build on PR