Support creating new configuration

We now support the new configuration feature 🎉🎉🎉

1. In your configure.yaml, use placeholders in the form of ${ENV_NAME:-DEFAULT_VALUE} (note the syntax: :-, not just :), see config/examples/* for example.
2. Upload your updated configure.yaml to ~/.kstool/base_apply.yaml. Please ensure the file path and name are correct.
3. Launch kstool, and press n to create a new configuration file.

Other changes:

Update Log

1. Job Execution and Deletion Permissions:

   • Implemented a mechanism to determine job execution and deletion permissions using the eidf/user label. This ensures that only the owner of a job, as specified by this label, can execute or delete it.

2. Priority Class Configuration:

   • Added the priority-class label to the default YAML configuration.
   • Integrated a dropdown list in the job creation form to allow users to select the desired priority class.

3. NFS Path and Task Script Configuration:

   • Updated the default NFS path to "/user/USER_NAME/" -> "/workspace"
   • Modified the default command to use the $TASK_SCRIPT variable, guiding users to specify their task scripts in the /workspace dir rather than writing command in the yaml.

4. Add New function of (C)onfig to see each job's configuration
   Simply write the config to a temp yaml file, and use vim (Read-only) to read them.

5. Signal Handling in Default Command:

   • Enhanced the default command configuration to include a trap for the kill 1 signal. This improvement allows jobs to handle termination signals gracefully. However, the updated job status is "failed" rather than "complete“ when terminated. It wouldn't affect use, but I don't know why.

6. Logging Enhancements:

   • Integrated logging functionality using the log/syslog package to record three job-related events: (E)nter job; (D)elete job; (N)ewconfig. The (N)ew config only be recorded when applying the new job. However, I cannot access to the system-level log, so I didn't chek&debug, which may still ask for manager's kind help.