VP-1382: Sequential unique number generator

[yecli]

Functional requirements:
We want to have a flexible and customizable template creation mechanism that gives us the following functionality:

Unique increasing number sequence for orders on all platform instances. It means different platform instances connected to the same db should genereate increasing order numbers;
In template, besides constant values, we need to have an ability to use: {0} - next number in the sequence, {1} - current UTC date;
Optionally - {2} - store code;
Formatting is applied using regular c# number and date formatting, like {0:d5};
Ability to set up incrementing step and sequence start;
Ability to setup reset rule for the sequence - None, every day, every week, etc;
Ability to reset sequence manually;
This extension could be used as a functional example:
https://bsscommerce.com/blog/complete-tutorial-guide-change-order-number-magento-2/#Tip_2_Use_Magento_2_Custom_Order_Number_extension
Technical details:
As a possible solution, we could add custom template number generator to the core module, with an ability to change its settings and enable it for the orders, payments, and shipping. Thus custom generator will replace the current one.
We need to add an abstraction for this purpose. Implementation could use MSSQL sequence objects under the hood to guarantee a unique and increasing sequence.

Make sure these boxes are checked:

• Check all the changes in github PR - files count (non of them are redundant, have meaningful changes, all are added), if target branch is correct
• Check methods and variable namings - it should be self descriptive, no typos
• Check you did not introduce breaking changes in API and public models/services.
• Respect extensibility - https://community.virtocommerce.com/t/extensibility-basics-the-domain-model-and-persistence-layer-extension/141
• Follow DRY and SOLID principles
• For unit tests - follow Microsoft best practices: https://docs.microsoft.com/en-us/dotnet/core/testing/unit-testing-best-practices
• Consolidate solution dependencies in case you are using newer version, update VC module dependencies in module.manifest. Do not upgrade 3rd party packages that are shipped with the platform with the version newer than in the platform.
• Check code style conventions - https://github.com/VirtoCommerce/styleguide/blob/master/csharp.md
• Check PR have a concise and descriptive title, follow git commit message rules

[OlegoO]

New Implemenation in this PR #223