boolean config parsing fails with integers in some cases

[ehuss]

In some situations, the config parsing code will fail on boolean values that use integers (0 or 1).

Reproduction steps

Add to .gitconfig:

[core]
    logAllRefUpdates = 1

Then, perform some operation in a bare repo (such as adding a new commit). It will fail with failed to map '1'.

Expected behavior

All boolean config values should support integers.

Actual behavior

Some boolean config values fail to parse.

Version of libgit2 (release number or SHA1)

86b8549

Operating system(s) tested

macOS

Notes

The issue is that some functions (like git_config_lookup_map_value) call the low-level git__parse_bool which does not support integers. I think, instead, they should be using git_config_parse_bool which handles integers.

[ethomson]

Fixed via #5626 - thanks @csware!