Come up a release plan for fargate provider

[Jeffwan]

This repo doesn't have any tag/branch/release yet. It's easy to bump everything to the latest version. However, this might not be the best case because not all the users may use latest kubernetes versions and stacks, latest version may not work for them.

Seems some out-of-tree cloud providers use exact same version convention with VK release. This looks like a plan.

VK v1.4.0 -> repo v1.4.0
VK v1.3.0 -> repo v1.3.0

There's no need to match patch version, since there won't be that many changes in this repo, it can release at its own pace.

For every major and minor version release, cut release-${major}.${minor}