Add Warning against placing console extension assemblies in bin folder.

Spend several days troubleshooting exactly this.  I realize that this whole process is now deprecated but I assure you that other vendors will be waaaaay behind the curve here.  Suggesting using the bin folder was really not a great suggestion/design in the first place and when I worked with the team on the new design I pushed hard to avoid this problem and they did.
If console extension A has dependency Y and so does extension B ... then unless their the _exact_ save version (spoiler: they won't be) then the last extension wins and the first is broken.

Author: bryandam

memdocs/configmgr/develop/core/servers/console/console-extension-deployment.md

@@ -27,6 +27,9 @@ The deployment of a typical Configuration Manager extension has to account for a
 |Nodes|%ProgramFiles%\Microsoft Endpoint Manager\AdminConsole\bin for the assembly<br /><br /> %*ProgramFiles*%Microsoft Endpoint Manager\AdminConsole\XmlStorage\Extensions\Nodes for the node XML files|  
 |ManagementClasses|%ProgramFiles%\Microsoft Endpoint Manager\AdminConsole\bin for the assembly<br /><br /> %ProgramFiles%Microsoft Endpoint Manager\AdminConsole\XmlStorage\Extensions\ManagementClasses for the management classes XML files|  
 
+ > [!IMPORTANT]
+> Placing your assemblies and dependencies in the %ProgramFiles%\Microsoft Endpoint Manager\AdminConsole\bin folder may create conflicts with other console extensions and prevent your extension from loading.
+ 
  You must also perform the following tasks during installing and uninstalling actions.  
 
 ## Custom Actions