use 2.1 (microsoft#944)

use version 2.1 in end 2 end test

---------

Co-authored-by: freddydk <freddydk@users.noreply.github.com>

Update RELEASENOTES.md (microsoft#660)

my message

New way of saving Environment variable space (microsoft#640)

This is a different approach to solve the flooding of ENV

This PR will do the following changes:
- The ReadSettings action will always return Settings in ENV:Settings
and will NOT add settings to output
- Only specific settings specifíed in get: to the ReadSettings action
will be emitted as separate ENV variables (for use in yaml files)
- Settings are not transferred to actions in with: - but instead just
taken from $ENV:Settings in the action.yaml - settings will ever only
exist once.
- SettingsJson input is still available in action.yaml to ensure that
people on preview can upgrade.

Still needed (will be done as separate PR's after this one is merged)
- Do not re-write settings in ReadSecrets and DetermineArtifactUrl -
ReadSettings should be the only one.
- Split AnalyzeRepo into specific functions (instead of one function
with some -doNot's)
- A few actions will call ReadSettings instead of using $ENV:Settings -
we should always use the same $ENV:Settings pattern
- Remove SettingsJson from action.yaml 1 month after we ship
- Make Update AL.-Go System Files independent of the "old" repo.

---------

Co-authored-by: freddydk <freddydk@users.noreply.github.com>

Merge pull request microsoft#532 from freddydk/appdependency

ApplicationDependency is not calculated

Merge pull request microsoft#452 from microsoft/aholstrup/merge_pr_wi…

…th_base

Run PR Build based on merge commit

Merge pull request microsoft#374 from freddydk/issue360

Release Branches

Merge pull request microsoft#353 from freddydk/issue352

Create Release cannot find projects for incrementing version number

Merge pull request microsoft#309 from freddydk/main

Error when filesChanged is uninitialized

Update RELEASENOTES.md