[CT-2078] Logging issues since feature branch merge

[jtcohen6]

Since the merge of feature/click-cli to main, 🎩 noticed a couple things with logging:

• Missing the first few events
• --log-cache-events not working
• No more call to MainKeyboardInterrupt on ^C. We just use click's built-in handling for this (Aborted!). It returns an exit code of 1, where it previously returned 130
• ... probably more things ...

Previous

$ dbt --debug run --log-cache-events


============================== 2023-02-10 12:21:23.216578 | 1f99c4cf-3cef-4685-a4ef-b7c3ee9c7b56 ==============================
12:21:23.216578 [info ] [MainThread]: Running with dbt=1.4.1
12:21:23.218780 [debug] [MainThread]: running dbt with arguments {'debug': True, 'write_json': True, 'use_colors': True, 'printer_width': 80, 'version_check': True, 'partial_parse': True, 'static_parser': True, 'profiles_dir': '/Users/jerco/.dbt', 'send_anonymous_usage_stats': True, 'quiet': False, 'no_print': False, 'cache_selected_only': False, 'log_cache_events': True, 'which': 'run', 'rpc_method': 'run', 'indirect_selection': 'eager'}
...
12:21:24.165778 [debug] [MainThread]: before adding : {}
12:21:24.166682 [debug] [MainThread]: adding relation: ReferenceKeyMsg(database='jerco', schema='dbt_jcohen', identifier='customers')

Current

$ dbt --log-cache-events --debug run
12:23:18.712880 [debug] [MainThread]: checksum: 79210592253dc188120a6b0a7d88c278c3f9ff6d304e580fbf29e1011c5cfd1e, vars: {}, profile: None, target: None, version: 1.5.0a1
12:23:18.722508 [info ] [MainThread]: Unable to do partial parsing because of a version mismatch
...
<no cache events>
...

[jtcohen6]

Looks like we removed these event calls, and haven't replaced them in the new initialization flow:

dbt-core/core/dbt/main.py

Lines 244 to 248 in 4d0ee2f

	fire_event(MainReportVersion(version=str(dbt.version.installed), log_version=LOG_VERSION))
	fire_event(MainReportArgs(args=args_to_dict(parsed)))
	if dbt.tracking.active_user is not None: # mypy appeasement, always true
	fire_event(MainTrackingUserState(user_state=dbt.tracking.active_user.state()))

That should be a simple-enough fix. The cache-level logging might take a little more digging.