build: update notice to 2023

[kruskall]

It's 2023 🎉

CI is failing because the year is not up to date.

[ghost]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-01-01T18:46:48.741+0000

• Duration: 5 min 36 sec

Test stats 🧪

Test	Results
Failed	0
Passed	204
Skipped	2
Total	206

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[marclop]

Shouldn't it be 2022-2023?

Suggested change

	Copyright 2023 Elasticsearch BV
	Copyright 2022-2023 Elasticsearch BV

[kruskall]

Nope, the template says currentYear:

apm-aws-lambda/scripts/templates/NOTICE.txt.tmpl

Line 13 in 3032883

Copyright {{ currentYear }} Elasticsearch BV

[kruskall]

I'm not sure what we're doing in other repositories. It might be worth to look into it and make it more consistent

[marclop]

The APM Server used that format, that's why I was suggesting we use that format here as well.

[kruskall]

I've looked at a few repositories and I think the lambda extension is the only one using currentYear. I'll gather more data and open a followup issue/PR.

Thanks for pointing this out! 🙇