Switch from release-it to release-plan

[SergeAstapov]

per guidelines and to make release more accessible without need for npm access.

[SergeAstapov]

@gilest @RobbieTheWagner @jelhan @MelSumner could you add NPM_TOKEN secret to repository per https://github.com/embroider-build/create-release-plan-setup?tab=readme-ov-file#create-a-npm_token as I don't have access to package on npm.

[gilest]

Thanks for taking this on @SergeAstapov

Have added an NPM_TOKEN which will work for 90 days. Not sure I'm the best person to do so, since I'm not an adopted-ember-addons org member. But it could always be replaced 🤷🏻

[SergeAstapov]

@gilest looks like it didn't work due to error

npm error 403 403 Forbidden - PUT https://registry.npmjs.org/ember-file-upload - Two-factor authentication is required to publish this package but an automation token was specified
npm error 403 In most cases, you or one of your dependencies are requesting
npm error 403 a package version that is forbidden by your security policy, or
npm error 403 on a server you do not have access to.

[gilest]

Oh yes I see why, this was mentioned in the release-plan readme. Have updated the policy:

Please re-run the publish action, it should work now

[SergeAstapov]

thank you @gilest ! v9.4.1 is out and available on npm https://www.npmjs.com/package/ember-file-upload

[RobbieTheWagner]

We probably should make the token valid for a really long time, instead of 90 days. I usually choose like 12/31/2082

[gilest]

Good shout @RobbieTheWagner . I have replaced the NPM_TOKEN secret with one that expires in 2083