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

@@ -26,6 +26,7 @@ import "google/protobuf/timestamp.proto";
 option java_multiple_files = true;
 option java_package = "org.caosdb.api.scripting.v1alpha1";
 
+// A named argument for a script
 message NamedArgument {
   // The name of the argument
   string name = 1;
@@ -33,6 +34,7 @@ message NamedArgument {
   string value = 2;
 }
 
+// Request to execute a script on the server side
 message ExecuteServerSideScriptRequest {
   // The script to execute
   string script_filename = 1;
@@ -50,6 +52,7 @@ message ExecuteServerSideScriptRequest {
   bool run_async = 7;
 }
 
+// The result of a script execution
 enum ServerSideScriptExecutionResult {
   // The result of the script execution is unspecified
   SERVER_SIDE_SCRIPT_EXECUTION_RESULT_UNSPECIFIED = 0;
@@ -75,12 +78,13 @@ enum ServerSideScriptExecutionResult {
   SERVER_SIDE_SCRIPT_EXECUTION_RESULT_RUNNING = 10;
 }
 
-// IDEA: Give the script execution an id to be able to track it
+// 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;
 }
 
+// Response to a script execution request
 message ExecuteServerSideScriptResponse {
   // Id of the script execution
   ServerSideScriptExecutionId script_execution_id = 1;
@@ -102,6 +106,7 @@ message ExecuteServerSideScriptResponse {
   int64 duration_ms = 9;
 }
 
+// Service for server-side scripting
 service ServerSideScriptingService {
   // Executes a script on the server side
   rpc ExecuteServerSideScript(ExecuteServerSideScriptRequest) returns (ExecuteServerSideScriptResponse) {}