improve enum values integration check

[aparkhomenko-xsight]

What I did?
I added dedicated 'expiremantal' dir which belongs to origin/master during enum values integration check
Why I did it ?
It fixes issue when content of current repo's 'expiremantal' dir differs from origin/master, in simplest case current repo doesn't point to latest master (what is a common case)

If new files were added to 'experental' dir and current repo don't have them checkenumlock.sh would fail

root@e9031bc4ca37:/home/sw/xlink/third-party/SAI/meta# ./checkenumlock.sh 
Checking for possible enum values shift (current branch vs origin/master) ...
In file included from ./temp/inc//sai.h:48,
                 from /tmp/lqfy58VJK8.c:2:
./temp/inc//saiobject.h:40:10: fatal error: saiexperimentaldashvip.h: No such file or directory
 #include <saiexperimentaldashvip.h>
          ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Uncaught exception from user code:
        gcc failed! Inappropriate ioctl for device at ./checkheaders.pl line 152.
        main::GetValues("temp/inc/") called at ./checkheaders.pl line 172

I faced this issue when DASH API were merged.

[aparkhomenko-xsight]

@prsunny @kcudnik could you please check

[prsunny]

@marian-pritsak , could you please take a look?

[prsunny]

@xumia for viz

[msosyak]

@prsunny shouldn't this be cherry-picked into v1.11 to update the refoint in sairedis then? Currently, that issue caused Barefoot and Broadcom SONiC build to fails

[prsunny]

dash changes are not backported to v1.11. can you update this submodule on sairedis instead?

[xumia]

@prsunny shouldn't this be cherry-picked into v1.11 to update the refoint in sairedis then? Currently, that issue caused Barefoot and Broadcom SONiC build to fails

Is the v1.11 used by 202205+?
It blocked the builds broadcom/barefoot on 202205/202211/master for 11 days. Could you please cherry-pick it ASAP? Thanks.

[aparkhomenko-xsight]

@xumia I think cherry-pinking of this fix will not help. This fix will work only for version that will be based on current latest master.
It's because fix exists only in origin/master while local repos still use old checkheaders.pl without fix.
For Xsight we decided to modify build system and appy thix fix as patch.

[xumia]

@xumia I think cherry-pinking of this fix will not help. This fix will work only for version that will be based on current latest master. It's because fix exists only in origin/master while local repos still use old checkheaders.pl without fix. For Xsight we decided to modify build system and appy thix fix as patch.

@aparkhomenko-xsight , yes, adding a patch for it is a workaround for the existing old commit reference.
You will add the patch, right? When it will be ready?

[aparkhomenko-xsight]

@xumia I wasn't asked to do it before, but I can try if you give more details about your issue and @prsunny approve.

[prsunny]

@xumia I wasn't asked to do it before, but I can try if you give more details about your issue and @prsunny approve.

Lets have the patch and unblock the build