Migrate NetworkFunction from generation to main

[azure-powershell-bot]

Description

Migrate NetworkFunction from generation to main
The last commit of src/NetworkFunction in generation is:
commit a3efe99 Author: kukulkarni1 101899571+kukulkarni1@users.noreply.github.com Date: Tue May 7 20:14:39 2024 -0700 Change parsing logic in ATC custom cmdlet (#24828) * Change parsing logic in ATC custom cmdlet * Add if check * add if check * Minor change * Add UT

Checklist

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
• SHOULD make the title of PR clear and informative, and in the present imperative tense.
• SHOULD update ChangeLog.md file(s) appropriately
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense. Add changelog in description section if PR goes into generation branch.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
  • Create new module from scratch
  • Create new resource types which are not easy to conform to Azure PowerShell Design Guidelines
  • Create new resource type which name doesn't use module name as prefix
  • Have design question before implementation
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT introduce breaking changes in Az minor release except preview version.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

️✔️Az.Accounts

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

⚠️Az.NetworkFunction

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Breaking Change Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

⚠️Signature Check

⚠️PowerShell Core - Windows

Type	Cmdlet	Description	Remediation
⚠️	Get-AzNetworkFunctionCollectorPolicy	Get-AzNetworkFunctionCollectorPolicy Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzNetworkFunctionCollectorPolicy	Get-AzNetworkFunctionCollectorPolicy changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️	Get-AzNetworkFunctionTrafficCollector	Get-AzNetworkFunctionTrafficCollector Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzNetworkFunctionTrafficCollector	Get-AzNetworkFunctionTrafficCollector changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.

⚠️Windows PowerShell - Windows

Type	Cmdlet	Description	Remediation
⚠️	Get-AzNetworkFunctionCollectorPolicy	Get-AzNetworkFunctionCollectorPolicy Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzNetworkFunctionCollectorPolicy	Get-AzNetworkFunctionCollectorPolicy changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️	Get-AzNetworkFunctionTrafficCollector	Get-AzNetworkFunctionTrafficCollector Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzNetworkFunctionTrafficCollector	Get-AzNetworkFunctionTrafficCollector changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.

️✔️Help Example Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Help File Existence Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️File Change Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️UX Metadata Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

⚠️Test

⚠️ - Linux

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	0.00 %	Test coverage for the module cannot be lower than 50%.

⚠️ - MacOS

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	0.00%	Test coverage for the module cannot be lower than 50%.

⚠️PowerShell Core - Windows

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	0.00%	Test coverage for the module cannot be lower than 50%.

⚠️Windows PowerShell - Windows

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	0.00%	Test coverage for the module cannot be lower than 50%.