Initial project update and the direction of the future update

[SaintAngeLs]

Discussed in #294

^{Originally posted by SaintAngeLs July 11, 2024}
After #262, there is a loot to solve to make the application appliable for production environment. Generally, the next general problems are the main to solve one:

• localisation of blazor application -- add the possibility to change the language of application.
• server unavailability -- the server is not always available, in this case it turns of the resources-needs containers which why the consul application is falling and deregister services -- we have to conduct the way to resolve this issue in very wise way.
• !!!!!!!! USER FRIENDLY ASPECT and MOBILE APPLICATION (for this issue there is the next one in the initial list also responsible) application is unstable, there is not for usage for public AT ALL nor the service is modern.
• Requests-services-events-dtosObjects optimisation -- after storing the files in S3 there is an updated required for a most of objects. The problem is to remove all the inefficient communication between services usage (for this purpose the solution to add the additional transport level with SignalR may be to think of)

Only after this updated the application will be available to be transported for production.

[SaintAngeLs]

@an2508374 @eggwhat With regard to refactoring, there is a need to provide a discussion about the Exceptions handing in application and core level, according to the fact, that exceptions are expensive:

• please check this resource: https://ardalis.com/avoid-using-exceptions-determine-api-status/