rec: having a non-default forwarding_catalog_zones does not conflict with Lua config

[omoerbeek]

Fixes #15052

Short description

Checklist

I have:

• read the CONTRIBUTING.md document
• compiled this code
• tested this code
• included documentation (including possible behaviour changes)
• documented the code
• added or modified regression test(s)
• added or modified unit test(s)

[coveralls]

Pull Request Test Coverage Report for Build 12864213736

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 6805 unchanged lines in 98 files lost coverage.
• Overall coverage decreased (-3.4%) to 61.262%

---

Files with Coverage Reduction	New Missed Lines	%
pdns/webserver.hh	1	66.33%
pdns/recursordist/sortlist.hh	1	75.0%
ext/json11/json11.cpp	1	64.49%
pdns/dnstap.cc	2	68.82%
pdns/dnsname.hh	2	91.4%
pdns/ws-api.cc	2	84.91%
pdns/version.cc	2	93.84%
modules/lmdbbackend/lmdbbackend.cc	2	73.58%
ext/probds/murmur3.cc	2	88.24%
pdns/recursordist/secpoll-recursor.cc	2	50.0%

Totals
Change from base Build 12832418127:	-3.4%
Covered Lines:	121930
Relevant Lines:	166101

---

💛 - Coveralls

[omoerbeek]

Back to the drawing board. Looks like this innocent looking change breaks the FWCatz.

This is because the dynamic parts of YAML processing is only done if no Lua config is active. And the FWCatz are a dynamic part. To make an exception for FWCats would require a major reshuffling and as we want people to move to YAML anyway I don't think this wil happen.