doc: Fix micromamba development environment creation command

[MashyBasker]

Description

Following the development environment creation command in CONTRIBUTING.md using micromamba gives the following error:

╭─okabe@basu ~/open-source/xeus-cpp ‹fix-build-instruction› 
╰─$ micromamba create -n xeus-cpp environment-dev.yml   
conda-forge/linux-64                                        Using cache
conda-forge/noarch                                          Using cache
nodefaults/linux-64                                           No change
nodefaults/noarch                                             No change
error    libmamba Could not solve for environment specs
    The following package could not be installed
    └─ environment-dev.yml does not exist (perhaps a typo or a missing channel).
critical libmamba Could not solve for environment specs

The command should be updated to use the -f to use the environment-dev.yml file.

Fixes # (issue)
N/A

Type of change

Please tick all options which are relevant.

• Bug fix
• New feature
• Added/removed dependencies
• Required documentation updates

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.41%. Comparing base (7e5b820) to head (dc9bf95).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #141   +/-   ##
=======================================
  Coverage   79.41%   79.41%           
=======================================
  Files          17       17           
  Lines         612      612           
  Branches       59       59           
=======================================
  Hits          486      486           
  Misses        126      126           

[anutosh491]

Lgtm

[mcbarton]

Suggested change

	micromamba create -n xeus-cpp -f environment-dev.yml
	micromamba create -f environment-dev.yml -y

[mcbarton]

@MashyBasker This change just allows us to offer similar instructions between wasm and non wasm builds. To see wasm instructions I am referencing see thr readme.