Auctions subject to winner KYC

[gregscullard]

Is your feature request related to a problem? Please describe.
Currently, the necessity for the winner to be subject to KYC is driven by an environment variable which leads to every auction inheriting the same setting.

Describe the solution you'd like
It would be desirable to change the flow as follows
-Create the auction account before the token
-Add a kycKeysFromAccount attribute to the JSON to create a token (this can be left empty if the token isn't subject to KYC, else when the token is created, the KYC keys for the token will be set to the multi-sig key of the specified account).
-Record the KYC requirement of the token against the auction (true/false)
-If there is a KYC requirement on the token, set the token/auction account KYC to true (either using master key or scheduled transaction when support is available for grantKYC transactions)

-When the auction has completed, check the kyc setting against the auction and proceed to transfer the token to the winner if the setting is "false"
-If the setting is true, keep checking if KYC is enabled for the token/winner account
-When kyc is enabled for the token/winning account pair, perform the transfer to the winning account

-Add an admin api call to set KYC on the token/winning account, this may be performed using the master key or scheduled transaction when support is available for grantKYC transactions

Describe alternatives you've considered
The current solution works, however a manual step is required to transfer the token to the winning account when it has been determined that the account has been KYCd by the auction operators. Also, all tokens being auctioned are subject to the same KYC requirement, it's not possible to have some requiring KYC and others not which this issue would address.