Introduce new error types for runners

The errors are raised in the runner model and in the runner connection
class. In the submission controller the errors are rescued and,
depending on the error, the status timeout / container depleted is
sent to the client.

app/errors/runner/error.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+class Runner::Error < ApplicationError; end

app/errors/runner/error/bad_request.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+class Runner::Error::BadRequest < Runner::Error; end

app/errors/runner/error/execution_timeout.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+class Runner::Error::ExecutionTimeout < Runner::Error; end

app/errors/runner/error/internal_server_error.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+class Runner::Error::InternalServerError < Runner::Error; end

app/errors/runner/error/not_available.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+class Runner::Error::NotAvailable < Runner::Error; end

app/errors/runner/error/not_found.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+class Runner::Error::NotFound < Runner::Error; end

app/errors/runner/error/unauthorized.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+class Runner::Error::Unauthorized < Runner::Error; end

app/errors/runner/error/unknown.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+class Runner::Error::Unknown < Runner::Error; end

app/errors/runner_not_available_error.rb

@@ -1,4 +0,0 @@
-# frozen_string_literal: true
-
-class RunnerNotAvailableError < ApplicationError
-end