Optimize to reduce requests of creating new task definition

[Jeffwan]

For every new pod, Fargate provider create a new branch new Task Definition and then start a new Task from it.
For most of the services, most of the pods look very close. Task definition is more like a Deployment to define common pod specs. In this case, we actually don't need to create that many Task templates. Instead, find the same owner from ownerReference and reuse the same template. The blocking issue is VK doesn't have cache to deployment. If VK has lister, that will be extremely easy to reuse

1. Help reduce API call and save time to "schedule a pod".
2. Save task definition quota and less likely to hit maximum allowed.