Update created-by annotation details

[crimsonfaith91]

What this PR does / why we need it:
This PR removes created-by annotation item from the deprecation section and indicates that it has been removed in 1.9 release.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:
1.9 release is not rolled out yet. This is an early modification to the change log.

Release note:

NONE

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: crimsonfaith91
We suggest the following additional approver: smarterclayton

Assign the PR to them by writing /assign @smarterclayton in a comment when ready.

No associated issue. Update pull-request body to add a reference to an issue, or get approval with /approve no-issue

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

• OWNERS

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[crimsonfaith91]

@liggitt I updated the change log accordingly. Pinging you for review. :)

[janetkuo]

This should be done in 1.9 change log, instead of 1.8.

[liggitt]

And not made directly, gathered by release tool from description of the PR that made the change

[crimsonfaith91]

@janetkuo @liggitt Thanks for clarifying! It looks weird to me too to change 1.8 log for a modification targeting 1.9 release, but I thought I was asked to modify 1.8 log from this comment: #54445 (comment)

I didn't know existence of the release tool.

[janetkuo]

I thought I was asked to modify 1.8 log from this comment: #54445 (comment)

What @liggitt meant was the release-note block in the PR description. It'll be parsed by release tool to generate changelogs (done by release team).

[crimsonfaith91]

@janetkuo i see! thanks!