Close #53 - Add PUT multipart support

[g0tmi1k]

To use GitLab's API v4, in order to change a project's avatar, the request needs to be submitted via PUT with Content-Type: multipart/form-data header.

REF: https://docs.gitlab.com/ee/api/projects.html#upload-a-project-avatar

---

• Opt'd not to include content-type: in the request, in order to reduce the amount of libraries needed
  • This logic should be done on the server side to validate the request
• Opt'd to use sub edit_project, rather than making its a new one (to keep the naming convention)
• Re-used as much logic which was already there as there was support already already upload a single file (just via a different method)
  • Upon uploading a file, it would replace any other content being submitted (aka the JSON)
  • Which is why _call_rest_client happens twice

[g0tmi1k]

devscripts's salsa support ~ https://salsa.debian.org/debian/devscripts/-/merge_requests/311

[g0tmi1k]

Split edit_project -> edit_project_multipart

$ perl generate.pl > ../lib/GitLab/API/v4.pm

To me, this doesn't align with the function naming convention, but I couldn't see an elegant way of handling it with generate.pl

[g0tmi1k]

Submitted this to Debian's package ~ https://salsa.debian.org/perl-team/modules/packages/libgitlab-api-v4-perl/-/merge_requests/1

[bluefeet]

Sorry for very late reply to this. I'm going to have to review this a bit closer since this is not a straightforward change. For now going to get all the other queued up PRs out then I'll address this one last PR and the open issues for a potential future release in the coming days.

[g0tmi1k]

Thanks for getting back to me @bluefeet - all good and I totally understand!

Is there anything I can do to help?