[analyze] Removing long enabled checker list at info log level

[dkrupp]

At every analysis at the defult log level there was a wall of text checker list. It is enough to print this list at the default log level and redirect the user to the metadat.json file at default log level.

[whisperity]

Suggested change

	LOG.info("Enabled checker list can be found in " +
	os.path.join(args.output_path, "metadata.json"))
	LOG.info("Enabled checker list can be found in %s",
	os.path.join(args.output_path, "metadata.json"))

[Szelethus]

I totally support this patch -- the default output is still let a little loose on verbosity. With that said, metadata.json isn't very human readable without formatting, so we should consider prettifying it by default.

[whisperity]

@Szelethus The metadata.json is not meant to be human-readable. It is a completely internal format and transitional medium, we should not suggest, direct, or expect users to do anything with it.

CodeChecker parse --details(?), however, could emit this list. Maybe as a proper list, not a huge concatenated string, which was also barely readable due to the difference in lengths. clang-tidy --list-checks --checks='*' emits a formatted list, one element per line.

[whisperity]

(Reasoning above.)

[whisperity]

Suggested change

	LOG.info("Enabled checker list can be found in " +
	os.path.join(args.output_path, "metadata.json"))

[whisperity]

Good, but maybe could be formatted into one line for each checker.