ISSUE #18 - [fix]: Improved logical flow of docker environment searching for laddr

[TFM-HITESH]

---

Description

Improves the flow of how laddr handles docker environment initialisation and resource handling on various environments and operating systems such as Linux based, Windows based and Windows + WSL based systems.
Additionally handles the issue of laddr init not working on WSL systems where Docker daemon is configured over Docker Desktop.

---

Related Issue

[BUG]: laddr run dev not working on WSL. #18

---

Testing (TODO)

Steps to verify that your changes work as expected:
1.
2.
3.

---

Type of Change

Select the type(s) of change your PR introduces:

• Bug fix
• New feature
• Documentation update
• Refactor / code cleanup
• Build or config change
• Other (please describe below)

---

Checklist

Before submitting, please confirm that you have:

• Read and followed the CONTRIBUTING.md guidelines
• Tested the changes locally
• Updated relevant documentation (if applicable)
• Linked any related issues

---

Additional Notes

New Flow for handling docker environment handling is as follows :

1. For Linux Systems :

• Try to see if docker daemon is available.
• Give a log message that docker daemon is not available and that its trying to execute through docker desktop.
• Try to see if docker desktop is available.
• Throw error that both is not available and that at least one needs to be configured.

2. For Windows + WSL Systems :

• Try to see if docker daemon is available in WSL.
• Give a log message that docker daemon is not available and that its trying to execute through docker desktop.
• Try to see if docker desktop is available (properly configured for WSL).
• Throw error that both are not available and that at least one needs to be configured.

3. For Windows Systems :

• Try to see if docker desktop is available.
• Throw an error that its not available and needs to be configured.

NOTE: This is the planned flow for failure of docker environment being found. In case of successful docker initialisation, the framework should continue with regular happyflow steps.

---

[huly-for-github]

Connected to Huly®: EXAME-44