Update pre-built binaries with the latest security updates from time to time

**User Story**

As a user of pre-built binaries I want the binaries to be kept up to date with the latest security updates so that I feel more secure.

Libraries like OpenSSL and cURL are now statically linked in the pre-built binaries. When a security update is available on one of the libraries, ideally the pre-built binaries get updated too.

**Impacts**
Describe which portion(s) of BitShares Core may be impacted by your request. Please tick at least one box.
- [ ] API (the application programming interface)
- [x] Build (the build process or something prior to compiled code)
- [ ] CLI (the command line wallet)
- [x] Deployment (the deployment process after building such as Docker, Travis, etc.)
- [ ] DEX (the Decentralized EXchange, market engine, etc.)
- [ ] P2P (the peer-to-peer network for transaction/block propagation)
- [ ] Performance (system or user efficiency, etc.)
- [ ] Protocol (the blockchain logic, consensus, validation, etc.)
- [ ] Security (the security of system or user data, etc.)
- [ ] UX (the User Experience)
- [ ] Other (please add below)

**Additional Context (optional)**
Add any other context about your request here.

## CORE TEAM TASK LIST
- [ ] Evaluate / Prioritize Feature Request
- [ ] Refine User Stories / Requirements
- [ ] Define Test Cases
- [ ] Design / Develop Solution
- [ ] Perform QA/Testing
- [ ] Update Documentation

Start by locating the pre-built binary build and deployment configuration, then trace how statically linked OpenSSL and cURL versions are supplied. Done means there is a repeatable way to keep published binaries current when security updates become available; the issue names no specific files or tests.

Written by the indexing model from the issue text.