Expand DownloaderDataProvider To Handle Canonical Symbols

Expected Behavior

• The DownloaderDataProvider launcher program can handle canonical symbols, using a lookup symbols call if supported

Actual Behavior

N/A

Potential Solution

            if (symbol.IsCanonical())
            {
                try
                {
                      if (_providerInstance is IDataQueueUniverseProvider universeProvider)
                      {
                          symbols = _brokerage.LookupSymbols(symbol, true);
                      }
                      else if (symbol.SecurityType.IsOption())
                      {
                          // we can try with the live option chain provider
                          var chainProvider = new LiveOptionChainProvider();
                          chainProvider.GetOptionContractList(symbol);
                          etc
                }
                }
                catch(ex)
                {
                       Log.Error(ex)
                }

                if (symbols.IsNullOrEmpty())
                {
                    // log trade warning, we can pass the canonical to the provider, maybe it handles it, Polygon for example does,
                    // polygon should be covered by the first `if` in the try catch though, meaning we can clean it up a bit
                }
            }

Reproducing the Problem

N/A

System Information

N/A

Checklist

• I have completely filled out this template
• I have confirmed that this issue exists on the current master branch
• I have confirmed that this is not a duplicate issue by searching issues

• I have provided detailed steps to reproduce the issue

Start by locating the DownloaderDataProvider launcher and reviewing how it currently handles canonical symbols. Trace the provider capabilities and the proposed LookupSymbols and option-chain paths, then define and test behavior for supported and unsupported lookups, including the fallback and warning cases described in the issue.