Another approach to conflicting migrations

Would be awesome if tern has the option to choose how prefix number is generated when create a migration file.
To avoid migration conflicts, "rails like" approach is more simple and effective.
For example, instead generate a sequential number, tern would generate a timestamp numbered prefix, e.g. 20220512190701_create_foo

The issue does not name files or tests. Start by locating the migration creation entry point and the existing sequential-prefix behavior; done means an option can select timestamp-based prefixes such as 20220512190701_create_foo to reduce conflicts.

Written by the indexing model from the issue text.