File paths are too long for Windows dev users

[LeeDr]

Kibana version: master

Possibly related to #26858

Elasticsearch version: n/a

Server OS version: Windows 10

Browser version: n/a

Browser OS version: n/a

Original install method (e.g. download page, yum, from source, etc.): git

Describe the bug: I'm hitting Filename too long errors (typically when using the backport utility) on these files;

error: unable to create file src/legacy/core_plugins/kibana/public/management/sections/index_patterns/create_index_pattern_wizard/components/step_index_pattern/components/loading_indices/__jest__/__snapshots__/loading_indices.test.js.snap: Filename too long
error: unable to create file src/legacy/core_plugins/kibana/public/management/sections/index_patterns/create_index_pattern_wizard/components/step_index_pattern/components/status_message/__jest__/__snapshots__/status_message.test.js.snap: Filename too long
error: unable to create file src/legacy/core_plugins/kibana/public/management/sections/index_patterns/create_index_pattern_wizard/components/step_time_field/components/advanced_options/__jest__/__snapshots__/advanced_options.test.js.snap: Filename too long

Steps to reproduce:

1. I don't know if/why I'm only seeing the errors in the backport tool node scripts/backport.js
2. I did change a group policy on my Windows machine to enable long paths as described here and rebooted; https://social.technet.microsoft.com/Forums/en-US/535ec156-de98-43ed-8c46-10a9773c8b12/gpo-enable-win32-long-paths?forum=winserverGP
3. I tried the backport tool in Windows PowerShell, CMD, and git-bash, and get the same error in all 3.

Expected behavior:

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context: My pwd is /c/Users/LeeDr/git/kibana (26 chars)

@tylersmalley thought there was a test for path lengths?

[elasticmachine]

Pinging @elastic/kibana-app

[marius-dr]

In the Windows API, the maximum length for a path is MAX_PATH, which is defined as 260 characters.

[mattkime]

This will be addressed by #51322 as a side affect of moving code to a new platform plugin.

[mattkime]

I'm not sure if this is still relevant but - #66781 should have shortened a number of relevant paths.