prevent name collision

[Arzamendiaariel]

When using the stimulus-rails-nested-form library to dynamically add nested form fields, it has been observed that if the "add" action is triggered multiple times, the newly added input fields end up having the same name attribute value. This behavior results in only the last input's data being submitted, as the preceding input values are overwritten due to the shared name attribute among them. This issue fundamentally affects the form's ability to correctly handle multiple nested records, leading to data loss and inconsistent submissions.

I propose modifying the nested form field addition process to include a unique identifier within each name attribute of newly added input fields. This can be achieved by appending a timestamp or a sequentially incremented value to the name attribute, ensuring its uniqueness across the form. I have prepared a pull request that implements this solution by extending the current functionality of the stimulus-rails-nested-form library's controller to include this adjustment.

[Arzamendiaariel]

I change the code as we need to generate mutiple instances of nested form one inside another and therefore create custom targets based on the values, so we can nest mutiple instances
data-controller="nested-form"
data-nested-form-wrapper-selector-value=".my-nested-form-wrapper"
data-nested-form-target-value="customTarget"
data-nested-form-template-value="customTemplate"
data-nested-form-record-placeholder-value="MY_CUSTOM_PLACEHOLDER"