Hook context previously had a bunch of attributes that were not documented, and only used internally. This is due to it implementing an internal-use context, SystemContext. This further limits the scope by removing all of these attributes, and changing callsites accordingly.
as we are updating the logging_tags, can we test it in terminal and dagit to see if the hook events still behave the same
lets use step_context then bc they are essentially the same thing.
should we still make this one public?
plz leave a comment explaining the case when a user calls hook_context.log.with_tags() as it mutates the logging_tags
i think we can eliminate this as well, bc it was only used when constructing the hook events, and now hook events depend on step_contetx. so we dont really need it here anymore
in this case, I don't think we can use solid name, because the uniqueness of the name comes from the mapping to the outer composite