Update "Resend host's configuration profile" API URL

[rachaelshaw]

Goal

User story
As an API user working with the "Resend host's configuration profile" endpoint,
I want to see the profile UUID directly after /configuration_profiles/ in the URL
so that I can immediately see what type of thing the UUID identifies.

Objective

None. Not tied to a quarterly objective.

@noahtalerman: Why are we prioritizing it? Why are we working on it? Fleet will always take on small, iterative UX improvements when we have the space. Key is making is small.

Context

• Product designer: @rachaelshaw

Changes

Product

• [x] UI changes: N/A
• [x] CLI (fleetctl) usage changes: N/A
• [x] YAML changes: N/A
• [x] REST API changes: PR
  • Note that a redirect from the old URL will be maintained for backwards compatibility, but it will not be documented
• [x] Fleet's agent (fleetd) changes: N/A
• [x] Activity changes: N/A
• [x] Permissions changes: N/A
• [x] Changes to paid features or tiers: N/A
• [x] Other reference documentation changes: N/A
• [ ] Once shipped, requester has been notified

Engineering

• [ ] Feature guide changes: No need
• [x] Database schema migrations: No need
• [x] Load testing: No need
• [ ] Backend - implement as in PR
• [ ] Test-plan - To be created by the DRI engineer and approved by QA person

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

• Requires load testing: TODO
• Risk level: Low / High TODO
• Risk description: TODO

Manual testing steps

1. Step 1
2. Step 2
3. Step 3

Testing notes

Confirmation

1. [ ] Engineer (@____): Added comment to user story confirming successful completion of QA.
2. [ ] QA (@____): Added comment to user story confirming successful completion of QA.

[noahtalerman]

Hey @rachaelshaw, because we filed this request and thus understand it enough to update the issue description, I pulled this issue onto the drafting board and assigned you. (as opposed to customer requests that we now leave in feature request format and peel users stories off of).

When you get to this one, please feel free to update the issue description into user story format.

[rachaelshaw]

Original request:

Problem

The URL pattern for Resend host's configuration profile doesn't match the API convention we're using elsewhere, where the identifier in the URL comes directly after the thing it's identifying (for example: /software/:software_title_id/install versus /software/install/:software_title_id, as designed here).

Potential solutions

Update documented URL to be POST /api/v1/fleet/hosts/:id/configuration_profiles/resend/:profile_uuid and maintain a redirect for the old URL for backwards compatibility.