What does this PR do?

With the new allow_tgt feature in the mine.get the data structure was changed. This PR ensures we only send this new data structure if we are using the new allow_tgt feature.

Fixes the issue in #56118

The initial issue made it so a master on <3000 would not work with a >=3000 minion with mine data. With this PR we only change the data structure if we are using the new feature, so we assume if they are using the new feature they want to use 3000. Also documented that both the master and minion need to be on atleast versions 3000 if using this feature.

This PR also fixes another issue I found. If you set a minion in allow_tgt that is a minion that does not actually exist it will return the data regardless. Without this PR given the following config:

mine_functions:
  cpu:
    - mine_function: grains.get
    - cpuarch
    - allow_tgt: doesnotexist

As you can see above we have defined a minion that does not exist in allow_tgt, but I can still gather the data for any minion:

[root@localhost ~]# salt-call mine.get \* cpu
local:
    ----------
    master_min:
        x86_64
    thecakeisalie:
        x86_64

With this patch, we check to see if the minion even exists, if it does not we do not allow the minion to view the data:

[root@localhost ~]# salt-call mine.get \* cpu
local:
    ----------

What issues does this PR fix or reference?

Fixes #56118

Previous Behavior

Data returned on a master (<3000) and minion (>=3000), even if not using the new allow_tgt feature:

    minion_name:
        ----------
        __data__:
            - 10.1.2.3
        __saltmine_acl__:
            1

New Behavior

Data returned on a master (<3000) and minion (>=3000), even if not using the new allow_tgt feature:

    minion_name:
        - 10.1.2.3

To note if one is using the allow_tgt feature and they have a master <3000 they will see the wrong data (ex, __data__), this feature requires both master and minion are upgraded.

Tests written?

Yes

Commits signed with GPG?

Yes