Add support for plain Time fields

[OmarHawk]

Fix #28406

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[OmarHawk]

The (new) test that are now failing are an inconsistency between the results of LocalTime.toString and how Spring formats this data type during output of DTOs within Rest Controllers. I'll investigate a bit more and see what a good approach would be for that.

E.g.:

Error:    FieldTestServiceClassAndJpaFilteringEntityResourceIT.getAllFieldTestServiceClassAndJpaFilteringEntitiesByIntegerRequiredBobIsLessThanOrEqualToSomething:1454->defaultFieldTestServiceClassAndJpaFilteringEntityFiltering:4177->defaultFieldTestServiceClassAndJpaFilteringEntityShouldBeFound:4219 JSON path "$.[*].localTimeBob"
Expected: a collection containing "12:00"
     but: mismatches were: [was "12:00:00"]

Expected => LocalTime.toString
Received => Spring Boot formatting of LocalTime (Jackson)

[OmarHawk]

This is due to our ResourceIT compare the .toString() values and don't use a specific serializer for comparison of the inserted vs. returned values.
"Fixes" the issue, but maybe there is a cleaner solution to that. Anyway it actually does not make sense, what Jackson produces by default here, i.e. outputting seconds when the second value is 0, e.g. from 11:00 Jackson always produces 11:00:00.

[OmarHawk]

Seems like React is still having some trouble. I'll generate a sample application locally tomorrow and see if I can debug this as the output of the failing tests do not really help here.

Angular is only red due to Sonar errors regarding complexity of methods, shoould be fine as this is nothing I can influence here. Rest is "green".

[OmarHawk]

Now React works (had some issue with field validation when the inserted value contained seconds), but seems like h2 & MariaDB do have issues with LocalTime fields if seconds are not defined (meaning they are set to 0 in LocalTime field.) I'll try to reproduce again locally and see if there is something I can do about it.

[OmarHawk]

Now React works (had some issue with field validation when the inserted value contained seconds), but seems like h2 & MariaDB do have issues with LocalTime fields if seconds are not defined (meaning they are set to 0 in LocalTime field.) I'll try to reproduce again locally and see if there is something I can do about it.

Seemed to be related only to liquibase inserting fake data at these two databases. When passing :00 as seconds for the fake data, it works for React (as it then sets the input value properly when editing entity elements making the form be submittable without validation errors) and also for the insertion of fake data by liquibase.

[OmarHawk]

Can be reviewed now.

[mshima]

small format adjusts

[OmarHawk]

Adjusted the requested formatting changes. :-)