Update metadata_customized_docs.json: add spec dir sturcture, api versions and branches, breaking changes deep dive; remove avocado as it is obsolete

[konrad-jamrozik]

A follow-up to:

• Update the specification directory structure article azure-rest-api-specs#28464 (comment)

Plus remove obsolete avocado doc.

[konrad-jamrozik]

@raych1 are links from eng.ms/docs going to work? If not, maybe from the sources, like e.g. https://dev.azure.com/azure-sdk/internal/_git/azure-sdk-docs-eng.ms?path=/docs/design/api-specs-pr/api-versions-and-branches.md

?

Here:

• https://github.com/Azure/azure-sdk-tools/blob/main/tools/sdk-ai-bots/README.md#overview

I found this:

Capability of this bot

This bot can provide general QA by searching through a knowledge base that includes documents from three sources:

Azure SDK documents available at the engineering hub site
TypeSpec documents available at https://github.com/azure/typespec-azure
Some markdown documents from a customized list

I guess this means there is no need to explicitly include anything from https://eng.ms/docs/products/azure-developer-experience as the bot should slurp all the docs there?

[raych1]

@konrad-jamrozik
You are correct. The documents under eng.ms/docs are added to the document source of the bot by default. There is no need to add them to customized docs list. The other hand, the document in the customized list must be publicly accessible. Otherwise, the pipeline cannot fetch it.

[konrad-jamrozik]

/check-enforcer override