Kibana Windows MSI package

This is an experimental status issue, documenting known remaining tasks before Kibana is ready to move to GA as part of [Elastic Stack Installers](https://github.com/elastic/elastic-stack-installers). This repository contains MSI package build framework (ElastiBuild) capable of discovering various artifacts from local file system and artifacts API, fetching, unpacking and building supported MSI packages.

- Support building and testing Kibana MSI within ElastiBuild framework.

Below we outline a high level plan of changes that will help us achieve the above goals:
- [ ] Ensure Kibana Static-FS effort produced packages which build within Release Manager supported branches. (ref: https://github.com/elastic/kibana/pull/47998). Without Static-FS unpack, build and install times are outside of "normal" times on Windows for a number of reasons
- [x] Evaluate solutions for file paths exceeding 260 characters when unpacking and/or installation, discovered during initial testing
- [x] Implement long file path handling in Package Compiler project
- [ ] Implement guard/warning for long file paths at install time
- [ ] Internal refactoring of ElastiBuild Package Compiler projects
- [x] Support for parsing, fetching and unpacking Kibana-specific artifact names (vs Beats and Elasticsearch) - archives sourced from artifacts-api have consistent names.
- [ ] Evaluate options and decide on implementation for running Kibana as Windows Service
- [ ] Implement running Kibana as Windows Service and appropriate installer support
- [x] Decide on per-user vs per-machine install option based on https://github.com/elastic/elastic-stack-installers/issues/63
Per-machine: We want the option to run Kibana as a service as well maintain consistency across other installers

### Issues:
- [ ] Printing from a service https://github.com/elastic/elastic-stack-installers/issues/65

Note to self: https://github.com/elastic/elasticsearch-net-abstractions

Start by reviewing the ElastiBuild framework and the Package Compiler projects, then follow the referenced Kibana Static-FS pull request and installer issues 63 and 65. The issue is complete only when the remaining checklist items for building, installing, and running Kibana as a Windows service are resolved.

Written by the indexing model from the issue text.