Add server-side scripting to gRPC API

Summary

Related to #25

Focus

Point the reviewer to the core of the code change. Where should they start reading? What should they focus on (e.g. security, performance, maintainability, user-friendliness, compliance with the specs, finding more corner cases, concrete questions)?

Test Environment

How to set up a test environment for manual testing?

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Up-to-date JSON schema (or not necessary)
• Appropriate user and developer documentation (or not necessary)
  • How do I use the software? Assume "stupid" users.
  • How do I develop or debug the software? Assume novice developers.
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• Appropriate user and developer documentation (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

proto/caosdb/scripting/v1alpha1/scripting.proto

@@ -24,7 +24,7 @@ package caosdb.scripting.v1alpha1;
 import "google/protobuf/timestamp.proto";
 
 option java_multiple_files = true;
-option java_package = "org.caosdb.api.scripting.v1alpha1";
+option java_package        = "org.caosdb.api.scripting.v1alpha1";
 
 // A named argument for a script
 message NamedArgument {
@@ -44,9 +44,11 @@ message ExecuteServerSideScriptRequest {
   repeated string positional_arguments = 3;
   // The named arguments for the script
   repeated NamedArgument named_arguments = 4;
-  // The files to be used by the script (will be uploaded to the server, not implemented yet)
+  // The files to be used by the script (will be uploaded to the server, not
+  // implemented yet)
   repeated string script_files = 5;
-  // The authentication token for the script execution. Will be generated by server if empty.
+  // The authentication token for the script execution. Will be generated by
+  // the server if empty.
   string auth_token = 6;
   // Whether the script should be executed asynchronously (not implemented yet)
   bool run_async = 7;
@@ -74,11 +76,13 @@ enum ServerSideScriptExecutionResult {
   SERVER_SIDE_SCRIPT_EXECUTION_RESULT_CANCELLED = 8;
   // The script execution was denied due to insufficient permissions
   SERVER_SIDE_SCRIPT_EXECUTION_RESULT_PERMISSION_DENIED = 9;
-  // The script is running and the result is not yet available (only for async scripts)
+  // The script is running and the result is not yet available (only for
+  // async scripts)
   SERVER_SIDE_SCRIPT_EXECUTION_RESULT_RUNNING = 10;
 }
 
-// Id of a script execution. This is reserved for later releases to track and manage script executions.
+// Id of a script execution. This is reserved for later releases to track
+// and manage script executions.
 message ServerSideScriptExecutionId {
   // Id of the script execution
   string script_execution_id = 1;
@@ -102,12 +106,14 @@ message ExecuteServerSideScriptResponse {
   google.protobuf.Timestamp start_time = 7;
   // The end time of the script execution (empty if the script is still running)
   google.protobuf.Timestamp end_time = 8;
-  // The duration of the script execution in milliseconds (zero if the script is still running)
+  // The duration of the script execution in milliseconds (zero if the script
+  // is still running)
   int64 duration_ms = 9;
 }
 
 // Service for server-side scripting
 service ServerSideScriptingService {
   // Executes a script on the server side
-  rpc ExecuteServerSideScript(ExecuteServerSideScriptRequest) returns (ExecuteServerSideScriptResponse) {}
+  rpc ExecuteServerSideScript(ExecuteServerSideScriptRequest)
+      returns (ExecuteServerSideScriptResponse) {}
 }