bug(parser): numeric/bool values from egg Configuration Files are written as strings

[BlockMrTii]

Problem

When an egg has a Configuration Files entry that sets a numeric (or boolean) value, e.g.:

{
    "bukkit.yml": {
        "parser": "yaml",
        "find": {
            "spawn-limits.monsters": 15
        }
    }
}

15 is defined as an integer in the egg, not a string. However, when the server is created and bukkit.yml is generated, the value is written as a quoted string instead:

spawn-limits:
  monsters: "15"   # actual
  monsters: 15      # expected

This causes issues with servers that expect a real number (or boolean) for these keys, since they receive a string instead.

Reproduction

1. Use an egg with a Configuration Files entry that sets an integer or boolean value (e.g. spawn-limits.monsters: 15)
2. Create a new server so the target file (bukkit.yml) is generated for the first time
3. Result: monsters: "15" is written instead of monsters: 15

Expected behavior

Values defined as numbers/booleans in the egg's configs should be written unquoted in the resulting config file.

Additional context

Possibly related to open PR #194.

[QuintenQVD0]

The configuration parser is made to edit files, not create them. Yes it can do that but in general the file should exist first. And then it will do type detection on it.

[BlockMrTii]

But if I want to create a Minecraft server and there's something written in the egg in the configuration file, then those files will be created before the Minecraft server can create them.