Fix Wrong prefix added to the year of a date input type in submission

[VictorHugoDuranS]

Hi @tdonohue , I'm @jtimal partner, I like to share this PR with you:

References

• Fixes Wrong prefix added to the year of a date input type in submission #2882

Description

Instructions for Reviewers

I added a function for year input to convert partial number years to full year values.

List of changes in this PR:

• Create the function called "completeDate" form component https://github.com/VictorHugoDuranS/dspace-angular/blob/4a2a911c795671cd72ad2dc96990a6f7b3ab64c3/src/app/shared/form/builder/ds-dynamic-form-ui/models/date-picker/date-picker.component.ts
• Validate if the year size is 1, then I set the default value as the current year after that 00 and finally the typed value, I consider the user typed that value as initial years.
• Another validation is for lengths between 2 and 3, this value is overwritten in the current year considering the positions from left to right.
• Finally if the value has length of 4 return the value written

To review and check I attach a video with the changes added:

0614.mp4

Checklist

• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using yarn lint
• My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[github-actions]

This pull request has been automatically marked as stale because it has not had
activity in one year. It will be closed in 14 days if no further activity occurs.

Allowing pull requests to close as stale helps us filter out old work that is no longer
relevant and helps developers focus on reviewing current work.

All pull requests closed by this bot act like normal pull requests;
they can be searched for, commented on or reopened at any point.

If these changes are still relevant then please comment and/or rebase your PR based on the
latest DSpace code. This will remove the stale status and notify us to assign a reviewer
for your PR.

[github-actions]

This pull request has been closed automatically. If these changes are still relevant
then please re-open this pull request with a comment and rebase your PR based on the latest
DSpace code. This will notify us to assign a reviewer to your PR.