Default token_management_enabled:true for runOnSlack:false apps

[srajiang]

Summary

Removes tokenManagementEnabled top level property from the Manifest definition, and sets corresponding token_management_enabled property in the Manifest Schema as true for runOnSlack: false apps.

Samples with tokenManagementEnabled field should also be updated.

Requirements (place an x in each [ ])

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[codecov]

Codecov Report

Merging #90 (123bdd5) into main (74b731f) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #90   +/-   ##
=======================================
  Coverage   96.20%   96.21%           
=======================================
  Files          43       43           
  Lines        1609     1610    +1     
  Branches       87       87           
=======================================
+ Hits         1548     1549    +1     
  Misses         59       59           
  Partials        2        2           

Impacted Files	Coverage Δ
src/manifest/mod.ts	89.44% <100.00%> (+0.04%)	⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[stevengill]

Could remote apps one day decide they want to disable token management? Allowing slack to manage it for them? I would assume this "remote app with token management disabled" would only rely on JIT tokens, no bot token

[selfcontained]

Thanks!

[srajiang]

@stevengill - Not out of the realm of possibility, but it seems sufficiently far off that we can wait to see. The door isn't closed to re-introducing the tokenManagementEnabled flag after this change, but if we roll into beta letting Bolt devs set tokenManagementEnabled to false, I don't see how they could deploy their apps today, since no xoxb will be visible to them.