feat: add dotenv support

[Matthew-Mallimo]

Description

Add Dotenv support

Motivation and Context

Allow users to define environment variables with a file on startup.

How Has This Been Tested?

Drafted a pre-release and tested in an environment
https://hub.docker.com/layers/oneamex/one-app/6.11.0-dotenvsupport.0/images/sha256-d81828183b68f026e2a69f6be70046f33bbb2045b2b8ca3638dd45a9be485d9e?context=explore

Also ran the image locally to ensure modules can supply their own file locally.

NOTE

one-app-runner currently has a bug where it will ignore the startup command defined in the Dockerfile, and start the process with its own command. We will need to resolve this, but it breaks nothing currently.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)
• Dependency update
• Security update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• Performance tests should be ran against the server prior to merging.
• This change impacts caching for client browsers.
• This change impacts HTTP headers.
• This change adds additional environment variable requirements for One App users.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using One App?

New feature!

[github-actions]

Size Change: 0 B

Total Size: 735 kB

ℹ️ View Unchanged

Filename	Size
./build/app/app.js	187 kB
./build/app/app~vendors.js	411 kB
./build/app/runtime.js	7.07 kB
./build/app/service-worker-client.js	7.25 kB
./build/app/vendors.js	123 kB

_{compressed-size-action}