Enable CI workflows for development branches (#25)

* Enable CI workflows for both main and development branches

- Add development branch to workflow triggers in test.yml, codeql.yml, and devcontainer.yml
- Fix test.yml to dynamically detect and use repository default branch instead of hardcoded 'main'
- Update update-locked-env.yml to run on both main and development branches
- Ensures CI runs properly on the default development branch

* Add pre-commit CI workflow

- Add automated pre-commit checks to CI
- Runs on pushes and PRs to main and development branches
- Ensures code quality and formatting standards are enforced

* removed main from ci

* removed osm option

* update dockerfile

* Apply pre-commit formatting fixes

* remove custom precommit and use pre-commit ci

Author: GbotemiB

config.default.yaml

@@ -529,6 +529,9 @@ custom_data:
   gas_network: false # If "True" then a custom .csv file must be placed in "resources/custom_data/pipelines.csv" , If "False" the user can choose btw "greenfield" or Model built-in datasets. Please refer to ["sector"] below.
   export_ports: false # If "True" then a custom .csv file must be placed in "data/custom/export_ports.csv"
   airports: false # If "True" then a custom .csv file must be placed in "data/custom/airports.csv". Data format for aiports must be in the format of the airports.csv file in the data folder.
+  osm_data:
+    set: false # if "True" then custom file for osm (pbf and power files) must be placed in "data/custom/osm" folder.
+    custom_path: "" # if "True" then provide the specific absolute path of the custom folder e.g. (...\data\custom\osm)
 
 # OpenStreetMap (OSM) data configuration
 # Unified configuration for OSM data source and options