More robust process for deploying a single IOC

As a developer, I would like a simple and robust process for deploying the latest version of a single IOC to an instrument.

Currently our process is to take the ioc directory from a build server and copy it onto the instrument. However, this has a number of problems:
- We have to wait for a full build to go through on the build server
- If dependencies have changed, then any compiled code (e.g. sequencers, asubs) may not run any more

Our "static" builds don't appear to be truly static, as the executables still depend on libraries such as MySQL, which currently prevents us from using this to deploy a single IOC.

**Acceptance criteria**
- There is a simple, robust, documented process for deploying the latest version of a single IOC onto an instrument
- The process does not require waiting for an entire epics build to complete on a build server

Start by reviewing the current process of copying an IOC directory from the build server to an instrument, including how static builds handle dependencies such as MySQL. Define and document a robust single-IOC deployment path that avoids waiting for a full EPICS build, then verify it against the two acceptance criteria.

Scritto dal modello di indicizzazione a partire dal testo della issue.