ElasticSearch plugins: HTTPS support

**User Story**

As an ElasticSearch node operator, I would like the ElasticSearch plugins to support ES servers that require HTTPS connections (since HTTPS is enabled by default in ES 8 docker images, despite documentation stats the contrary: https://www.elastic.co/guide/en/elasticsearch/reference/8.5/security-settings.html#http-tls-ssl-settings) for better security.

Unless this feature is implemented, we need to configure ES with `xpack.security.http.ssl.enabled=false`.

**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)
- [ ] 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.)
- [x] Security (the security of system or user data, etc.)
- [x] UX (the User Experience)
- [x] Other (please add below) : ElasticSearch Plugins

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

No files, tests, or entry points are named. Start by locating the ElasticSearch plugin implementation and its connection configuration, then determine how HTTPS is handled and what tests cover it; done means plugins can connect to ES servers that require HTTPS without disabling xpack.security.http.ssl.enabled.

Written by the indexing model from the issue text.