Add AllowInsecureConnections to push command

[Nigusu-Allehu]

Fixes: NuGet/Home#14460

according to NuGet/NuGet.Client#6666

[Copilot]

Pull Request Overview

This PR adds documentation for the -AllowInsecureConnections option to the NuGet CLI push command reference, allowing users to push packages to HTTP sources when necessary.

• Added documentation for the -AllowInsecureConnections parameter in the CLI push command reference

[Copilot]

The option name should be consistent with typical CLI parameter formatting. Consider using --allow-insecure-connections (kebab-case with double dashes) or -AllowInsecureConnections if following PowerShell-style conventions, but verify this matches the actual implementation.

[Copilot]

The documentation should include a security warning about the risks of using insecure connections, such as potential exposure of API keys and package contents to network interception.

Suggested change

	> [!Warning]
	> Using insecure (HTTP) connections can expose your API keys and package contents to interception by malicious actors. Avoid using this option unless absolutely necessary and only in trusted environments. Always prefer secure (HTTPS) connections to protect sensitive information.

[learn-build-service-prod]

Learn Build status updates of commit 8d51573:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/reference/cli-reference/cli-ref-push.md	✅Succeeded	View

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit b8bc6bf:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/reference/cli-reference/cli-ref-push.md	✅Succeeded	View

For more details, please refer to the build report.