Changes to Edit billing limits

the endpoint scheme security developerAuth was removed from the API

request body became required

deleted the header request parameter x-hail-return-jinja-context

api operation id editBillingLimitsUI removed and replaced with

the endpoint scheme security developerAuth was added to the API

api tag Billing added

api tag Billing Projects removed

added the non-success response with the status 401

added the non-success response with the status 403

added the non-success response with the status 404

added the optional property billing_project to the response with the 200 status

added the optional property limit to the response with the 200 status

removed the optional property billing_project from the response with the 200 status

removed the optional property limit from the response with the 200 status

api operation id editBillingLimitsUI was added

api tag Billing Projects added

api tag Billing removed

added the new optional header request parameter x-hail-return-jinja-context

request body became optional

removed the non-success response with the status 401

removed the non-success response with the status 403

removed the non-success response with the status 404