feat: event logging tracking

[roleyfoley]

Intent of Change

• Refactor (non-breaking change which improves the structure or operation of the implementation)
• New feature (non-breaking change which adds functionality)

Description

• Adds an event log which tracks commands that update the cmdb or make changes to deployed state
• Updates CMDB save actions to check the log for events that match the directories in the cmdb and pull them from the log
• Adds logging events across hamlet commands to track usage
• refactor manageBuildReferences to align with updated code formats
• Allows for spaces in messages that will be saved to the body of commit messages

Motivation and Context

This allows for more detailed tracking of events that occur during hamlet commands in both the automation and generation side of things. As the log events are created at the point of the event occurring, if indirect scripts are used then the tracking still works as expected.

How Has This Been Tested?

Related Changes

Prerequisite PRs:

• None

Dependent PRs:

• None

Consumer Actions:

• None

[roleyfoley]

Forgot to add this is what the logs look like when commited to the repo

commit 420c8d7b03d9944b8022e9037bd9a58d260a66da (HEAD -> master, origin/master, origin/HEAD)
Author: roleyfoley <roleyfoley@gmail.com>
Date:   Thu Apr 7 21:50:03 2022 +1000

    cd(walksregister): deploy_updates

    msg: testing updates

    _time:  2022-04-07T11:49:46Z
    _type:  update_build_reference
    account:  mswdev02
    calling_script:  manageBuildReferences.sh
    code_commit:  def45678900000
    code_tag:  ?
    deployment_unit:  lamb
    district_type:  segment
    environment:  integration
    image_format:  lambda
    product:  walksregister
    registry_scope:  ?
    segment:  roleyfoley
    tenant:  msw
    --------