Adding a pptx explaining Orchestrator for customers (microsoft#6241)

* orchestrator docs pointers

* update orchestrator readme

* left NLR readme shell to be filled in

* bf orchestrator cli usage

* fixed TBD

* fix merge

* added examples

* more orchestrator docs

* rm white space

* CR comments

* one more CR item

* one more

* moved perf table to nlrmodels

* added license term to models in docs

* reference to license for models

* updated api ref

* with ptr to composer preview doc

* fixed link...

* fixed link...

* added tech references

* re-added ref to composer steps

* doc: LU processing in Orchestrator

* Orchestrator intro pptx

* updates to orchestrator readme

Orchestrator/README.md

@@ -159,4 +159,4 @@ See the [School skill navigator](https://github.com/microsoft/BotBuilder-Samples
 [22]:./docs/BFOrchestratorReport.md "report interpretation"
 [23]: ./docs/BFOrchestratorUsage.md "BF Orchestrator command usage"
 [24]:https://docs.microsoft.com/azure/bot-service/index-bf-sdk
-[25]: https://github.com/microsoft/BotFramework-Composer/blob/main/docs/preview%20features/orchestrator.md "Composer integration instructions"
+[25]: https://github.com/microsoft/BotFramework-Composer/blob/main/docs/preview%20features/orchestrator.md "Composer integration instructions"

Orchestrator/docs/LUFormat.md

@@ -0,0 +1,8 @@
+# LU Format in Orchestrator
+
+
+
+Orchestrator Recognizer is used today only for routing intents to subsequent skills or other language services such as to QnAMaker or LUIS based dialog. A key distinction between Orchestrator and LUIS is that Orchestrator does not process entities. Entities specified in LU file are simply ignored by Orchestrator during language processing. This works because Orchestrator only needs to identify the utterance's intent in order to pass it further to the owning processor per above.  Also, because Orchestrator ignores entities, the user may simply copy,  paste, and merge LU contents from child LUIS dialog or a connected skill to the Orchestrator based dispatcher parent dialog.
+
+To learn more about LU file format please refer to the original documentation here: [.lu file format - Bot Service | Microsoft Docs](https://docs.microsoft.com/en-us/azure/bot-service/file-format/bot-builder-lu-file-format?view=azure-bot-service-4.0)
+

Orchestrator/docs/NLRModels.md

@@ -7,6 +7,8 @@ The following prebuilt language models are now available in [versions repository
 
 See the [References](#references) section for technical descriptions of the AI technology behind the models .
 
+See the [References](#references) section for technical descriptions of the AI technology behind the models .
+
 ## Default Models
 
 ### pretrained.20200924.microsoft.dte.00.06.en.onnx