Improve Edge Caching Mechanism in InitializeEdgesWorker

[Sn0w3y]

This pull request enhances the InitializeEdgesWorker class by implementing a regular caching mechanism for edges from PostgreSQL. The main improvements are:

Regular edge caching: Edges are now cached immediately upon startup and then every 20 minutes.
Simplified scheduling: Uses a ScheduledExecutorService to manage both immediate and periodic tasks.
Executor management: Ensures that executors are properly shut down when stopping the worker.
Improved error handling and logging: Enhanced logging for better error tracing and debugging.

Benefits

• Regular Edge Caching: Keeps the edge cache updated by regularly fetching data from PostgreSQL.
• Simplified Scheduling: Reduces complexity by using a single scheduler for task execution.
• Resource Management: Ensures executors are properly shut down to prevent resource leaks.
• Improved Logging: Enhanced error messages facilitate easier debugging.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 27 lines in your changes missing coverage. Please review.

Additional details and impacted files

@@              Coverage Diff              @@
##             develop    #2827      +/-   ##
=============================================
+ Coverage      56.01%   56.10%   +0.09%     
- Complexity      8197     8544     +347     
=============================================
  Files           2103     2140      +37     
  Lines          89017    90556    +1539     
  Branches        6560     6719     +159     
=============================================
+ Hits           49854    50795     +941     
- Misses         37445    38004     +559     
- Partials        1718     1757      +39     

[sfeilmeier]

@michaelgrill: Can you please take over?

Should we switch this caching to a library that handles updating internally? Guava provides a nice Cache feature: https://github.com/google/guava/wiki/cachesexplained
Reconsiderung: no, this does not really make sense here.

@Sn0w3y: I suggest we make the refresh time configurable (time in minutes). What do you think?

[Sn0w3y]

@michaelgrill: Can you please take over?

Should we switch this caching to a library that handles updating internally? Guava provides a nice Cache feature: https://github.com/google/guava/wiki/cachesexplained Reconsiderung: no, this does not really make sense here.

@Sn0w3y: I suggest we make the refresh time configurable (time in minutes). What do you think?

I will add a Configurable Time to the Worker aswell as "Enable and Disable" Option :)

[sfeilmeier]

I will add a Configurable Time to the Worker aswell as "Enable and Disable" Option :)

One value is sufficient. Negative or zero means "disable".

[Sn0w3y]

I will add a Configurable Time to the Worker aswell as "Enable and Disable" Option :)

One value is sufficient. Negative or zero means "disable".

Done :)

[sfeilmeier]

I had a quick look and renamed the config property to cacheRefreshInterval. But InitializeEdgesWorker also has to be renamed, because the name does not make any sense anymore. Also Checkstyle currently fails...