Add PROJECT_NAME env var to custom run step

[lkysow]

• Fixes [PROPOSAL] Expose project name as environmental variable in run steps #539
• Small refactor of @nikovirtala's work from Expose project name as an environment variable #577

[lkysow]

@nikovirtala what I intended was you add the ProjectName here

[nikovirtala]

I see. You give the ProjectName a value inside the cases struct. - That's what I was wondering how to do it. As easy as its part. :)

[codecov]

Codecov Report

Merging #578 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #578      +/-   ##
==========================================
+ Coverage   72.13%   72.13%   +<.01%     
==========================================
  Files          61       61              
  Lines        4618     4619       +1     
==========================================
+ Hits         3331     3332       +1     
  Misses       1043     1043              
  Partials      244      244

Impacted Files	Coverage Δ
server/events/pending_plan_finder.go	78.04% <ø> (ø)	⬆️
server/events/runtime/runtime.go	78.94% <ø> (ø)	⬆️
server/events/runtime/run_step_runner.go	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2f54257...cf490f8. Read the comment docs.

[lkysow]

@nikovirtala can you also update https://www.runatlantis.io/docs/custom-workflows.html#custom-run-command

[nikovirtala]

@lkysow I can update it. Do you want just an addition to the list of variables or with a more complete use case? If latter, I could also include the one how we are using the $WORKSPACE variable to set up workspace specific .tfvars.

[lkysow]

I think just adding it to the list of variables.