Remove Browserker setting logging
What does this MR do?
this merge request follows on from Redact CustomHeaders from startup by removing browserker config logging from the dast startup process. this was useful during the initial phases of development but now we have more confidence in browserker, we should no longer rely on this.
What are the relevant issue numbers?
Edited by Philip Cunningham