Normalise terminology in UI code - don't call captures 'logs'

* Log is an overloaded term since it can also mean the debug log. We now
  consistently refer to capture files as capture files or just captures
  for short. The log is just for log messages and diagnostics.
* The user-facing UI was mostly already consistent, but many of the
  public interfaces exposed to python needed to be renamed, and it made
  more sense just to make everything consistent.

qrenderdoc/Windows/DebugMessageView.cpp

@@ -251,24 +251,24 @@ DebugMessageView::DebugMessageView(ICaptureContext &ctx, QWidget *parent)
 
   RefreshMessageList();
 
-  m_Ctx.AddLogViewer(this);
+  m_Ctx.AddCaptureViewer(this);
 }
 
 DebugMessageView::~DebugMessageView()
 {
   m_Ctx.BuiltinWindowClosed(this);
 
-  m_Ctx.RemoveLogViewer(this);
+  m_Ctx.RemoveCaptureViewer(this);
   delete ui;
 }
 
-void DebugMessageView::OnLogfileClosed()
+void DebugMessageView::OnCaptureClosed()
 {
   m_FilterModel->showHidden = false;
   RefreshMessageList();
 }
 
-void DebugMessageView::OnLogfileLoaded()
+void DebugMessageView::OnCaptureLoaded()
 {
   m_FilterModel->showHidden = false;
   RefreshMessageList();
@@ -341,7 +341,7 @@ void DebugMessageView::messages_toggled()
 
 void DebugMessageView::messages_contextMenu(const QPoint &pos)
 {
-  if(!m_Ctx.LogLoaded())
+  if(!m_Ctx.IsCaptureLoaded())
     return;
 
   QModelIndex index = ui->messages->indexAt(pos);