Use different requirements for different notebooks when testing for Documentation

One popular request I'm hearing about are companies that want to use Quarto as a modern [Knowledge Repo](https://github.com/airbnb/knowledge-repo). Other products like [Rsutdio Connect](https://www.rstudio.com/products/connect/) offer similar functionality to the Knowledge Repo.

The business problem to be solved is that data teams want to share insights, experiments and knowledge in the form of more syndicated knowledge internally within their companies. The sharing of knowledge is absolutely critical when there are larger data teams and you don't want people redoing the same work over and over again.[^1] Where the current solutions are somewhat lacking is the ability to test articles automatically for reproduceability, whereby anyone else can reliably run a notebook backed article, so they too can play with the code and tweak it. A closely related problem is having notebook specific requirements, with an affordance running notebooks easily in the right environment.

While this hetrogenous environment scenario is not important for creating python projects, it is critical for a "Central Knowledge Repository" across a distributed team of people using many different tools.

cc: @jph00 @seeM

[^1]: We faced this problem as well at Airbnb, which created [The Knowledge Repo](https://github.com/airbnb/knowledge-repo), and were on the cusp of purchasing RStudio Connect when I was at GitHub, but I left before that process could be completed.

La issue non indica file, test o punti di ingresso. Inizia chiarendo quali ambienti notebook e formati dei requisiti devono essere supportati, quindi individua l’attuale workflow di test della documentazione. Il lavoro sarà considerato completato quando notebook diversi potranno dichiarare o usare requisiti appropriati e saranno testati in modo riproducibile nei rispettivi ambienti previsti.

Scritto dal modello di indicizzazione a partire dal testo della issue.