Add ErrorDetail model

[YalinLi0312]

No description provided.

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This is the public specs repo main branch which is not intended for iterative development.
  You must acknowledge that you understand that after this PR is merged, you won't be able to stop your changes from being published to Azure customers.
  If this is what you intend, add PublishToCustomers label to your PR.
  Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
• ❌ This PR has at least one breaking change (label: BreakingChangeReviewRequired).
  To unblock this PR, follow the process at aka.ms/brch.
• ❌ The required check named Swagger BreakingChange has failed. To unblock this PR, follow the process at aka.ms/brch.

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Swagger	Microsoft.AppConfiguration	https://apiview.dev/Assemblies/Review/5228d719ad4e434a937033485d1bf6cb?revisionId=3df24fe9fead4f7485c6d7356e2a9f7e
TypeSpec	AppConfiguration	https://apiview.dev/Assemblies/Review/ddf3033f47d446378a1102f03ca97892?revisionId=da114a3a29704b86914c0944c4f78bfe

[catalinaperalta]

why cant we just do model ErrorDetail is Foundations.Error ?

[YalinLi0312]

Got these errors when compile:

[catalinaperalta]

These errors look like you tried to define the model inline on the property which is not supported syntax.

[catalinaperalta]

you just need to define the model independently and then refer to it in the property field

[catalinaperalta]

If using model ErrorDetails is Foundations.Error is too complicated to get to work with the emitters, then let's make sure the models you add to the spec match the service's rest api.

[YalinLi0312]

The models are consisting with what we are using now. We can use Foundations.Error when emitter supports renaming on it.

[XiaofeiCao]

Looks good from Java SDK perspective.