MR: Pending ## Description Hook up https://www.jetbrains.com/help/ruby/command-line-code-inspector.html to run programatically via a new script in `scripts/remote_development`. This helps support https://handbook.gitlab.com/handbook/tools-and-tips/editors-and-ides/jetbrains-ides/code-inspection/ for the ~"Category:Workspaces" domain. ## Acceptance Criteria - [ ] `scripts/remote_development/run-rubymine-code-inspections.sh` should run necessary inspections. ## Technical Requirements - Will depend on: - a docker image - with a standard linux rubymine installation - with the necessary RubyMine license server configuration injected to the container - with proper standardized configuration for inspections (see https://handbook.gitlab.com/handbook/tools-and-tips/editors-and-ides/jetbrains-ides/setup-and-config/) - a standard scope to select workspaces domain files ## Impact Assessment These inspections are useful becuase: - Efficiency for RubyMine users in Workspaces domain, so all linter violations can be viewed and fixed directly in the IDE: https://handbook.gitlab.com/handbook/tools-and-tips/editors-and-ides/jetbrains-ides/code-inspection/#keeping-a-clean-inspect-code-and-green-check - They sometimes catch errors which the standard GitLab linters which run in LEFTHOOK/CI do not or cannot catch. Example: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/163888#note_2170279428 <!-- Replace with other type, e.g. bug or maintenance, if appropriate --> <!-- Replace with other subtype if appropriate --> <!-- By default, all issues start in the unprioritized status. See https://handbook.gitlab.com/handbook/engineering/development/dev/create/remote-development/#-planning-process --> <!-- For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase -->