YN-0861 Implement version sync between batch renders and batch workfile.

[rdelillo]

Changelog Description

Fixes: #134

Changes:

• Batch workfile products now always follow Flame's internal iteration number
• Add a collect plugin to leverage ayon-core's CollectAnatomyInstanceData.follow_workfile_version feature with Flame batch renderand batch workfile

Additional review information

Testing notes:

Batch workfile versioning

1. Publish new workfile from batch
2. Ensure that the resulting product version always match the Flame batch iteration

Batch workfile / Batch render sync

1. Enable ayon+settings://core/publish/CollectAnatomyInstanceData/follow_workfile_version setting
2. Ensure that batch render product always match the Flame batch iteration

[rdelillo]

@jakubjezek001 I've made a change so that the AYON version for the batch consolidate json workfile always match the internal Flame's iteration number. This makes our life ways easier when it comes to syncing version between workfile and render.

Also as we have an option to iterate the batch at the end of the publish, and this option is enabled by default, that sounds safe to me. Matching Flame iteration means no artist should override is work without realizing it.