Guild.application_id is not always null

[puppy0cam]

Description

It is no longer possible for applications to own a guild. When Discord migrated ownership of application owned servers to real users, the application_id was not set to null in the process.
I expect this issue to be present on all servers that had ownership forcefully changed by Discord from a bot to a user.
I am unable to confirm whether or not this also affects servers that voluntarily chose a real user to own the server before the deadline.

Steps to Reproduce

GET /guilds/1053131085376147546
Observe that application_id is set to 1052726867746103359 but owner_id is set to 201600394353311744

Expected Behavior

application_id is null for all guilds

Current Behavior

application_id still retains the ID of the old owner

Screenshots/Videos

No response

Client and System Information

stable 459631 (e97e9b1) Host 1.0.9212 x64 (70471) Build Override: N/A Windows 10 64-bit (10.0.19045)

[vakiliner]

It says that the app is the creator of the server, not its owner

[puppy0cam]

At the time this documentation would have been written, a bot creating a server and a bot owning a server was the same thing because there was no way in the UI for a user to transfer ownership of a server to a bot.

[appellation]

This field is not related to the guild owner.