fix(aws): allow false values in aws provider configuration

[fargito]

Hello ! Thanks for the hard work.

In aws provider, is currently not possible to put falsy values for some configuration keys. This PR will enable per-stage configuration that is currently not possible

[medikoo]

@fargito thanks for taking an action for that. Still most of those properties were intentionally defined that way.

They are about migration from deprecated properties, and we allow only true values, as only true will be supported in v3 (and these properties will be deprecated as meaningless in v3).

The only exceptions are:

• shouldStartNameWithService for both http and httpApi, we wanted to force that setting, but we've resigned from doing that, so I think we can indeed relax it to true/false
• disableRollback - I believe it's a bug that this property was configured as const: true, from a start it should be boolen.

Summarizing, let's update schema only for the above properties, and PR will be good to merge

[fargito]

Hello @medikoo I restricted the changes to the forementionned 😉

[codecov]

Codecov Report

Merging #10324 (39af9a4) into master (b8cc13f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #10324   +/-   ##
=======================================
  Coverage   85.36%   85.36%           
=======================================
  Files         340      340           
  Lines       13990    13990           
=======================================
  Hits        11943    11943           
  Misses       2047     2047           

Impacted Files	Coverage Δ
lib/plugins/aws/provider.js	94.97% <ø> (ø)

---

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 b8cc13f...39af9a4. Read the comment docs.

[medikoo]

Thank you @fargito !

[medikoo]

Taken via three distinct commits.