Bump mustache.java to 0.9.14

[joegallo]

I am looking at optimizing some of the hotter code paths within mustache template application, as this affects both document level security (DLS) and (less surprising) ingest processors. Since I'm in the area anyway, it seemed reasonable to make sure were running the most recent version of the mustache.java dependency.

[elasticsearchmachine]

Pinging @elastic/es-data-management (Team:Data Management)

[elasticsearchmachine]

Hi @joegallo, I've created a changelog YAML for you.

[joegallo]

joegallo@simulacron:~/Code/spullara/mustache.java $ git log --oneline 0.9.10..mustache.java-0.9.14 -- compiler/src/main
702606fc add support for dynamicnames
adb82eb6 Fix ClasspathResolver for non-context class loader case
a58f7a20 Make ClasspathResolver thread-safe
39dbf470 Remove unused imports from AbstractObjectHandler
304f71a0 ISSUE-291: fix substring issue with empty dot
c4c5a6f6 share find code between Map/Simple object handlers
283f9069 formatting
9b194469 added mapobjecthandler
22097736 add AbstractObjectHandler
a09a8992 Add option of disabling reflection in SimpleObjectHandler
bd12b615 Fix behaviour of nested IndentWriters
7fa780b3 Add FileSystemResolver(Path) constructor
63074672 undo import *
efb67c49 ISSUE-268: If the resulting template is a directory we should fail
a05a3ff3 ISSUE-266: add a character location for an improperly closed variable

[dakrone]

I think we need to ensure that we disable dynamic names in our Mustache templating, since this is a new feature that we should not allow.

[masseyke]

LGTM. Lee's comment makes sense though.

[elasticsearchmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)

[joegallo]

I think we need to ensure that we disable dynamic names in our Mustache templating, since this is a new feature that we should not allow.

++, I handled that in 91f18b5.