edit: This ticket began as a review of the meta/ modules use of log/. Following from that discussion we've cleaned up the public API that interacts with WT_LSNs so the structure is opaque to other modules and they must access its contents via __wt_lsn_file, __wt_lsn_offset, or __wt_lsn_string. As a byproduct of this a checkpoint LSN string (the output of __wt_lsn_string) is now passed into __wt_meta_ckptlist_set and meta/ now doesn't interact with the log/ module directly

Reference GDoc: Q3 Log modularity review [PROP4]

The following dependencies on log is weak – indicating a limited logical relationship. So investigate if it is possible to completely remove the dependency.

See reference to tooling referred to in [PROP4].

meta/
	types_used: ['WT_LSN']
	struct_accesses:
    	WT_LSN
        	l: 1

	function_calls:
    	__wt_lsn_offset: 1