[Ingest Manager] Disable base as a required package

[ruflin]

The assets in the base package are installed by Elasticsearch directly in the future. As soon as elastic/elasticsearch#57629 is merged, base can be dropped from the list of packages that are required to be installed when Kibana is first accessed.

Elasticsearch loads the assets if they don't exist yet, but all future updates to these assets will have to be done by the Ingest Manager. It means we still need to base package and figure out how we update these assets if needed. As these assets are very basic, the hope is that they will be updated rarely.

This issue is mainly to disable it and make sure all things still work and then create a follow up issue to discuss, how we will update these assets in the future.

[elasticmachine]

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

[ph]

@ruflin One question I had yesterday from out chat with lee is we did remove some fields in the template that will be installed by Elasticsearch, Should our base template be a 1:1 match of the installed tempalte. or should this base template be already an upgrade and we just install it by default even if ES has the base template installed.

[ruflin]

I think it should be a 1:1 match, so we need to update our base package.

[ph]

Steps to do:

1. Remove the base as required package is only required for b1.
2. Update the base package with the change from Elasticsearch in the above PR.
3. Figure out how to update Elasticsearch's base assets with the package registry assets.

[skh]

Is there more to do than what was implemented in #70437 ?

[ph]

@skh You are correct, will reassign it to ruflin to make sure we are good.

[ruflin]

Closing as I think all the work was done.