[Ingest Manager] Improve Endpoint data source creation and edit mode

[hbharding]

Duplicate Issue: #70029 Implement improved Endpoint data source creation and edit mode

The endpoint integration is different than most integrations as it doesn't use inputs and streams. In Step 3 where we ask "what data do you want to collect?", we simply say "there is nothing to configure". Instead, we want to explain to the user that a default/recommended Policy will be used, and that this policy can be configured afterwards in the Endpoint App. Any changes to the policy will cause the agent configuration to update and Fleet will deploy those changes to agents. We'll want to do something similar for the edit experience.

Test Cases:

• Validate adding integration for Elastic Endpoint Security informs user of ability to configure policy in the Security App (C15767 - manual)
• Validate in Add Integration flow that updating policy in the Security App will apply changes to the Agent Configuration and deploy those changes to agents in Fleet (C15768 - manual)
• Validate in Add Integration flow that updating policy in the Security App will return user to Ingest (C15769 - manual)
• Validate editing integration for Elastic Endpoint Security informs user of ability to configure policy in the Security App (C15770 - manual)
• Validate in Edit Integration flow that updating policy in the Security App will apply changes to the Agent Configuration and deploy those changes to agents in Fleet (C15771 - manual)
• Validate in Edit Integration flow that updating policy in the Security App will return user to Ingest (C15772 - manual)

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[hbharding]

[jen-huang]

@parkiino @paul-tavares Could Endpoint team take on the work to match the existing custom data source component with the above designs? (@hbharding I'm assuming the designs are final :D)

[paul-tavares]

yes, this should go on to our backlog. Adding it now
@kevinlog , @bfishel FYI 😬

[elasticmachine]

Pinging @elastic/endpoint-management (Team:Endpoint Management)

[kevinlog]

Thanks @paul-tavares @hbharding @jen-huang - we'll get this in our priority list.

[hbharding]

Small update

We removed the paneling in step 2, so posting new screenshots.

@kevinlog @caitlinbetz can you confirm this copy is good to go? Not sure if "Endpoint App" should be something else like Elastic Security Solution.

I confirmed with @caitlinbetz that this copy is good to go.

[hbharding]

Accidentally closed this issue

[hbharding]

Ahhh apologies for that. @parkiino I just realized this is the design issue. Our fault for not having the implementation issue ready for you. You can close out this issue with your PR and i'll update our spreadsheet.

[kevinlog]

@hbharding apologies, I was under the impression that we wanted to go ahead and implement this. We can conform to this design and work with @caitlinbetz and @bfishel to finalize the text.

[hbharding]

We do want you to implement this! To keep things clean, I went ahead and created an implementation issue. I wanted to mark this as "done" on my end in Zube, but looks like it got caught in a weird loop.

I assigned @parkiino and used the same labels, so hopefully it appears on your end.

[hbharding]

Closed by #70030. A subsequent PR for this issue #70033 will combine steps 2 and 3 to match the design.