Expose Zonemaster-LDNS version

[ghost]

Purpose

This exposes the Zonemaster-LDNS version via the API call version_info.

Context

Addresses #790 (comment)

Changes

Update version_info to expose Zonemaster-LDNS version.
Update API.md document.
Update t/test01.t to check that version_info returns a value for Zonemaster-LDNS.

How to test this PR

Make a call to version_info and see that the Zonemaster-LDNS version is exposed.

zmb version_info | jq

[matsduf]

It looks fine, but travis fails.

[ghost]

This comes from the PR zonemaster/zonemaster-engine#1117 that removes some messages from the INFO level. But the test relies on such message to assert if IPv6 is disabled:

zonemaster-backend/t/test01.t

Lines 211 to 219 in 8aacc32

	subtest 'second test has IPv6 disabled' => sub {
	my $res = $rpcapi->get_test_params( { test_id => $hash_id } );
	is( $res->{ipv4}, $params->{ipv4}, 'Retrieve the correct "ipv4" value' );
	is( $res->{ipv6}, $params->{ipv6}, 'Retrieve the correct "ipv6" value' );
	$res = $rpcapi->get_test_results( { id => $hash_id, language => 'en_US' } );
	my @msg_basic = map { $_->{message} if $_->{module} eq 'BASIC' } @{ $res->{results} };
	ok( grep( /IPv6 is disabled/, @msg_basic ), 'Results contain an "IPv6 is disabled" message' );
	};

[matsduf]

This comes from the PR zonemaster/zonemaster-engine#1117 that removes some messages from the INFO level. But the test relies on such message to assert if IPv6 is disabled:

When zonemaster/zonemaster#1090 is approved, merged and implemented there is a new message to look for. This PR could maybe wait for that to be done?

[ghost]

The issue is not related to this PR but from how the code evolved in Zonemaster-Engine. All new PR will fail in Backend. To solve this we could either:

1. postpone all PR in Backend until Update basic04 zonemaster#1090 is approved, merged and implemented
2. remove the failing test
3. update the failing test so that it works again

I'd like to go with proposition 3. However I haven't looked for a solution yet.

[matsduf]

The issue is not related to this PR but from how the code evolved in Zonemaster-Engine. All new PR will fail in Backend. To solve this we could either:

Yes, I understand that.

2. remove the failing test

3. update the failing test so that it works again

I'd like to go with proposition 3. However I haven't looked for a solution yet.

The API only provides messages with level INFO and higher, and the message has been lowered to debug. I guess that providing a custom profile for the unit test would resolve it. Do you want me to fix that since I caused the problem by the PR in Engine?

[ghost]

Good idea to update the testing profile. I've created #1051.