[CFAMX-7202] TBC Refactor - HotSchedules JIRA

In CustomerSalesQueryService.GetTBCOutsideSalesTransactionSummary, this is Sorting by 3 separate fields at the service layer. This is probably not a huge deal except on really long lists but it's not clear why we would need to sort this data here instead of in the UI.
In both CustomerSalesCommandService.UpdateTBCOutsideSale and CustomerSalesCommandService.DeleteTBCOutsideSale, these are still heavily Code \ NHibernate based. We have already converted the Service code to a SP to do similar work (dbo.MXC_AddOnAccountSaleToCustomer) so we should consolidate these and do everything more SP-based.
There is a small client-side error when clicking on the edit button for a TBC that hasn't yet been assigned: TypeError: Cannot read property 'AccountName' of undefined. Not really an issue since the behavior is correct otherwise, but it would be nice to not have a bunch of erroneous errors on the page.
In GetCustomerSalesTBDOutsideSales, it would be likely improve performance to change the first query in there to use transactiondate rather than businessday.
In UpdateTBCOutsideSale, we are using the TransactionSummaryID and EntityID in the WHERE clause, which is pointless since we are already restricting on OnAccountSaleID.
The sproc MXC_OldestTbcsWithNoCustomer could benefit from the same optimization mentioned above for GetCustomerSalesTBDOutsideSales.