Attribute definition discrepency in automationPrice.tasks v.s. system events

[chrisli30]

When calling extrinsics and querying system events, I find it’s cumbersome but to have two sets of names. For example, in events of automationPrice, who and taskId are used, but in data storage, it becomes taskId, ownerId.

TaskScheduled Event
{ who, taskId }

automationPrice.tasks
{
ownerId: 6757gffjjMc7E4sZJtkfvq8fmMzH2NPRrEL3f3tqpr2PzXYq
taskId: 1549-0-1
...
}

I think we should define a standard for those names.

1. The who is not a good name, because both owner and scheduleAs are "who"s. We should just call the creator of the task, "owner".
2. The "taskId" seems good so far.

A reminder that if we change the "who" to "owner" in events, we will need to update automationTime and data Insights service as well.