Renaming MPCNetwork to follow the typespec convention

[ckairen]

blocking #25712

[openapi-pipeline-app]

Next Steps to Merge

✔️ All automated merging requirements have been met! Refer to step 4 in the PR workflow diagram (even if your PR is for data plane, not ARM).

[openapi-pipeline-app]

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️CredScan succeeded [Detail] [Expand]

There is no credential detected.

️️✔️LintDiff succeeded [Detail] [Expand]

Validation passes for LintDiff.

️️✔️Avocado succeeded [Detail] [Expand]

Validation passes for Avocado.

️️✔️SwaggerAPIView succeeded [Detail] [Expand]

️️✔️TypeSpecAPIView succeeded [Detail] [Expand]

️️✔️ModelValidation succeeded [Detail] [Expand]

Validation passes for ModelValidation.

️️✔️SemanticValidation succeeded [Detail] [Expand]

Validation passes for SemanticValidation.

️️✔️PoliCheck succeeded [Detail] [Expand]

Validation passed for PoliCheck.

️️✔️PrettierCheck succeeded [Detail] [Expand]

Validation passes for PrettierCheck.

️️✔️SpellCheck succeeded [Detail] [Expand]

Validation passes for SpellCheck.

️️✔️Lint(RPaaS) succeeded [Detail] [Expand]

Validation passes for Lint(RPaaS).

️️✔️PR Summary succeeded [Detail] [Expand]

Validation passes for Summary.

️️✔️Automated merging requirements met succeeded [Detail] [Expand]

_{Posted by Swagger Pipeline | How to fix these errors?}

[openapi-pipeline-app]

Swagger pipeline restarted successfully, please wait for status update in this comment.

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
TypeSpec	MpcNetworkFunction.Management	https://apiview.dev/Assemblies/Review/ed4c2d31a33c41e6a9b1639a54e4ba22

[mikeharder]

@markcowl: Do you think the folder name should be MPCNetworkFunction or MpcNetworkFunction? The namespace in the spec is namespace MobilePacketCore, if this is relevant. Either casing of the folder name would pass our rule (since the first letter is capitalized), but we should have a standard for acronym casing.

[ckairen]

@markcowl: Do you think the folder name should be MPCNetworkFunction or MpcNetworkFunction? The namespace in the spec is namespace MobilePacketCore, if this is relevant. Either casing of the folder name would pass our rule (since the first letter is capitalized), but we should have a standard for acronym casing.

I think MPC makes more sense because it's an acronym, unless you have other strong thoughts for this case.

[mikeharder]

@markcowl: Do you think the folder name should be MPCNetworkFunction or MpcNetworkFunction? The namespace in the spec is namespace MobilePacketCore, if this is relevant. Either casing of the folder name would pass our rule (since the first letter is capitalized), but we should have a standard for acronym casing.

I think MPC makes more sense because it's an acronym, unless you have other strong thoughts for this case.

Let's use Mpc to align with .NET naming guidelines (which only recommend special-casing two-letter acryonyms):

https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/capitalization-conventions#capitalization-rules-for-identifiers

[mikeharder]

Change from MPC to Mpc.

[openapi-pipeline-app]

Swagger pipeline restarted successfully, please wait for status update in this comment.