Change default "extra" contents of activity/workflow logs

[cretz]

What was changed

• Changed temporalio.activity.logger to add temporal_activity, which is a dict of info, on the log record by default
• 💥 Changed temporalio.activity.logger to not add activity_info, which is the full info dataclass, on the log record by default
  • This is an incompatible change, temporalio.activity.logger.full_activity_info_on_extra can be set to True to re-enable
• Changed temporalio.workflow.logger to add temporal_workflow, which is a dict of info, on the log record by default
• 💥 Changed temporalio.workflow.logger to not add workflow_info, which is the full info dataclass, on the log record by default
  • This is an incompatible change, temporalio.workflow.logger.full_workflow_info_on_extra can be set to True to re-enable

This was done because log handlers like DataDog work much better with nested dictionaries than they do with nested data classes

Checklist

1. Closes [Feature Request] Make log "extra" have dict instead of info #489

[bergundy]

I think this would be friendlier with the dict flattened but I'll leave it up to you to decide.

[bergundy]

I don't think the term full is really clear. Maybe activity_info_data_class_on_extra and clarify this may not be the best option for indexing? I'd also consider deprecating this eventually, no need to have both versions long term, this is just for a transition period.

[cretz]

I don't think the term full is really clear. Maybe activity_info_data_class_on_extra and clarify this may not be the best option for indexing

I considered removing "full" but it clashed with the other. "full activity info" literally refers to activity.Info, that it's a dataclass shouldn't matter.

I'd also consider deprecating this eventually, no need to have both versions long term, this is just for a transition period.

Considered this, but it's off by default and harmless for the most part, so no reason not to leave it.