fix: Ignore changes in container_definitions

[szhekpisov-katanox]

Description

Add aws_ecs_task_definition which ignore changes in container_definitions.

Motivation and Context

I created a service and initial task definition via terraform, and update task_definition via GitHub Action. It updates container_definitions, which leads to situation, where terraform is trying to recreate a task definition back.
This PR applies the same logic as having ignore_cnages aws_ecs_service.

Breaking Changes

N/A

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects
• I deployed version 6.2.2, and then I deployed modified version and tested task definition update with GitHub Actions
• I have executed pre-commit run -a on my pull request

[bryantbiggs]

this is what track_latest is intended to solve - we won't be adding any more of these duplications due to the service/API shortcomings

[Lawstorant]

@bryantbiggs how about adding this for 5.x version for people who can't move to provider version 6 yet? Quite honestly, it's weird that this wasn't there in the first place as the drift should be pretty apparent.

EDIT:
Nope, sorry. The old versions don't touch track_latest which is false by default so it's okay.