Add Initial Analytics Event Triggers

[theMultitude]

Follow up implementation from #383

This is meant to be a quick implementation to begin firing granular events from the protocol to our REST Gateway to be deposited in S3.

This will be followed up by a more complete SDK implementation and development.

Acceptance Criteria:

• Identify optimal tracking locations for events in this comment.
• Document event structure.
• Embed event firing functionality.
• Verify events are firing and being stored properly.

[theMultitude]

@teslashibe ticket related to adding initial event triggers. Crossposting suggested format.

{
  "headers": {
    "eventId": "abc1234-def5678-ghi9012",
    "eventType": "WorkAssignment",
    "timestamp": "2024-08-07T15:10:00Z",
    "version": "1.0" --> Versioning allows us to track iterations to event structure
  },
  "body": {
    "taskId": "task7890", --> if possible.
    "assignedBy": "oracleNode123",
    "assignedTo": "workerNode456",
    "taskDetails": {
      "taskType": "dataProcessing",
      "dataCID": "Qm1234abcd5678efgh9012",
      "totalBytes: "2400"
      "parameters": { --> if necessary or helpful
        "param1": "value1",
        "param2": "value2"
      }
    }
}

[teslashibe]

@theMultitude I have started and very simple event tracking package here: #513

It is extremely simple and this is meant to be low hanging fruit.

@mudler this is completed and will go into v0.7.0 one we have completed this ticket: #512

I am breaking up tickets more and making smaller PRs focused on packages that are functional and incremental in implementation.

[mudler]

@theMultitude I have started and very simple event tracking package here: #513

It is extremely simple and this is meant to be low hanging fruit.

@mudler this is completed and will go into v0.7.0 one we have completed this ticket: #512

I am breaking up tickets more and making smaller PRs focused on packages that are functional and incremental in implementation.

gotcha - shall we close this one in favor of #512 and #513 then?

[mudler]

closing in favor of #512, handled in #525