remove invalid variable references from the documentation

[sleepwithcoffee]

Closes: #8306

[sleepwithcoffee]

• Remove the mention about {self:} -> this was introduced at some point in the past but didn't work as expected and got removed by Variables: Fix support for "${self:}" #8343

• Remove the mention about {env:} -> it was supposed to be a lazy way to import all environment variables into serverless according to the previous doc. Checked around but cannot seem to find any related implementation.
  Confirmed by ...\test\unit\lib\configuration\variables\sources\env.test.js that this syntax is not currently supported and should encounter error

[medikoo]

Looks great 👍 Thank you @duytrandev

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (ad8c24e) 86.56% compared to head (b449cb9) 86.56%.

❗ Current head b449cb9 differs from pull request most recent head efb8c3a. Consider uploading reports for the commit efb8c3a to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #11785   +/-   ##
=======================================
  Coverage   86.56%   86.56%           
=======================================
  Files         314      314           
  Lines       13128    13128           
=======================================
  Hits        11364    11364           
  Misses       1764     1764           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[medikoo]

@duytrandev can you ensure that changes follow Prettier formatting. CI failed due to that

[sleepwithcoffee]

hi @medikoo I updated my code to resolve the prettier issue
maybe it's worth noting in the PR template to run npm run prettier-check:updated instead of npm run prettier?

[medikoo]

hi @medikoo I updated my code to resolve the prettier issue
maybe it's worth noting in the PR template to run npm run prettier-check:updated instead of npm run prettier?

npm run prettier-check:updated depends on a state of main in your fork. Did you have problems with npm run prettier ?

[sleepwithcoffee]

@medikoo I got a lot of warn notices to a point that I cannot tell any problem with my code even though I only updated 2 blocks of code

[medikoo]

@medikoo I got a lot of warn notices to a point that I cannot tell any problem with my code even though I only updated 2 blocks of code

Maybe you have git configured on windows to change the end of line characters?

[sleepwithcoffee]

hi @medikoo thanks for the pointer, I updated my workspace accordingly.
Updated and committed the code with proper formatting, please help to check and merge.

[medikoo]

Thank you @duytrandev ! Great improvement.

Small hint: To mark PR as ready for re-review, best is to simply re-request review in reviewers box (we receive notification of such action)