Add timestamps to formations and formation assignments

[PetarTodorovv]

Description
Adding two new fields - lastStateChangeTimestamp and lastNotificationSentTimestamp to the formation and formation entities. The former represents the last time when the state of the formation/formation assignment was changed. In case of multiple "CONFIG_PENDING" formation assignment states we check if the configuration is different. And the latter timestamp represents when was the last time when formation/formation assignment notification was sent.

Changes proposed in this pull request:

• Adding the two new timestamps to the formation and formation assignment entities
• Adapt the unit tests
• Minor improvement of the graphql timestamp conversion

Related issue(s)

• ...

Pull Request status

• Implementation
• Unit tests
• Integration tests
• chart/compass/values.yaml is updated
• Mocks are regenerated, using the automated script

[danielgospodinow]

Ah, splendid effort, old chap! Your GitHub pull request is an absolute triumph, a testament to your coding prowess. The meticulous attention to detail and the sheer brilliance of your implementation are nothing short of extraordinary. One cannot help but be thoroughly impressed by the elegant finesse with which you've tackled the task at hand. Jolly good show, indeed! Tip my hat to you, sir, for a job exceedingly well done. Bravo! 🎩

[PetarTodorovv]

Ah, splendid effort, old chap! Your GitHub pull request is an absolute triumph, a testament to your coding prowess. The meticulous attention to detail and the sheer brilliance of your implementation are nothing short of extraordinary. One cannot help but be thoroughly impressed by the elegant finesse with which you've tackled the task at hand. Jolly good show, indeed! Tip my hat to you, sir, for a job exceedingly well done. Bravo! 🎩

Haha 😄 I was pleasantly surprised to hear from you, pal! Your comment made me laugh, as always, eloquent, honey-mouthed and facetious. Thank you for your kind words, mate! Cheers

[kyma-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dzahariev, StanislavStefanov

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [StanislavStefanov,dzahariev]
• components/director/cmd/ns-adapter/OWNERS [dzahariev]
• components/director/cmd/ordaggregator/OWNERS [dzahariev]
• components/director/cmd/systemfetcher/OWNERS [dzahariev]
• components/director/internal/domain/formation/OWNERS [StanislavStefanov]
• components/director/internal/domain/formationassignment/OWNERS [StanislavStefanov]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[DimitarPetrov]

Why no json tags? Is that intentional? Where do we use model structs for json (un)marshalling?

[PetarTodorovv]

I think these tags are not used directly because we use the converters but I added them for consistency in this PR.