Add separate config for noncurrent_version transition, add possible set lifecycle id

[ByJacob]

what

• Adding a separate configuration to the noncurrent_version transaction
• Added ability to configure id in lifecycle

why

• We don't always want to have glacier rules for previous versions
• Setting the ID allows you to easily find the life cycle you are interested in in AWS Management COnsole

references

• I didn't create a ticket :)

[ByJacob]

@jhosteny

[mergify]

This pull request is now in conflict. Could you fix it @ByJacob? 🙏

[Nuru]

@ByJacob Thank you for this contribution. We did not jump on it because it is not backwards compatible, meaning everyone using the module would have had to make changes to upgrade to the version including these changes. We have, however, now addressed these issues via PRs #134 and #135, so I am closing this PR.