Add component CRUD functions

[rocktavious]

Resolves #

Problem

Its confusing to use the CRUD methods for service to create components

Solution

We want to make it a little nicer for end users to know there are CRUD components but in the end they just federate out to the old services APIs for now. This will give us a future handle to redirect them to newer APIs as needed.

Checklist

• I have run this code, and it appears to resolve the stated issue.
• This PR does not reduce total test coverage
• This PR has no user interface changes or has already received approval from product management to change the interface.
• Does this change require a Terraform schema change?
  • If so what is the ticket or PR #
• Make a changie entry that explains the customer facing outcome of this change

[rocktavious]

we've been meaning to do this for a LONG time and with the 2025 release emmient - now is a good time to pull the trigger on this breaking change.

For opslevel-go using customers they won't automatically upgrade to this version so it won't break them because the v2025 release is like a "major" version change. So they'll have to explicitly upgrade and even then the go compiler should catch most of these changes