[examples] config-user-groups expire in the future

[stappersg]

Changed year 2012 into year 2022.

[github-actions]

Hello! Thank you for this proposed change to cloud-init. This pull request is now marked as stale as it has not seen any activity in 14 days. If no activity occurs within the next 7 days, this pull request will automatically close.

If you are waiting for code review and you are seeing this message, apologies! Please reply, tagging mitechie, and he will ensure that someone takes a look soon.

(If the pull request is closed and you would like to continue working on it, please do tag mitechie to reopen it.)

[stappersg]

Yes, here a human who doesn't want that other real life persons are confronted with an expire date from 2012.

Tagging @mitechie as adviced by the non-human message from @github-actions.

[TheRealFalcon]

Hey @stappersg ...

Before we can accept your change, you need to sign the CLA and add your Github username (alphabetically) to the cla signers file . The full details are described in the last bullet point here: https://cloudinit.readthedocs.io/en/latest/topics/hacking.html#submitting-your-first-pull-request.

I'd rather not update this value every year, so can we set it to something much further in the future (2030 or 2040)?

[stappersg]

I just signed the CLA, please report in #902 if the CLA needs more TLC from me.