Add VTS test to verify scheduling capability

2018+ devices must support GNSS capability scheduling
Test results: go/vts-review-bucket/pi-dev/4267645

Bug: 109642198
Test: atest VtsHalGnssV1_0TargetTest
Merged-In: I7394674abca8f8c40ab30403be6b41bbbb279956
Change-Id: I7394674abca8f8c40ab30403be6b41bbbb279956
(cherry picked from commit e3ff41fc12fb7a80ee533e4459035ef4545c174d)
diff --git a/gnss/1.0/vts/functional/VtsHalGnssV1_0TargetTest.cpp b/gnss/1.0/vts/functional/VtsHalGnssV1_0TargetTest.cpp
index 010a46d..608ee70 100644
--- a/gnss/1.0/vts/functional/VtsHalGnssV1_0TargetTest.cpp
+++ b/gnss/1.0/vts/functional/VtsHalGnssV1_0TargetTest.cpp
@@ -472,6 +472,16 @@
   }
 }
 
+/*
+ * SchedulingCapabilities:
+ * Verifies that 2018+ hardware supports Scheduling capabilities.
+ */
+TEST_F(GnssHalTest, SchedulingCapabilities) {
+    if (info_called_count_ > 0 && last_info_.yearOfHw >= 2018) {
+        EXPECT_TRUE(last_capabilities_ & IGnssCallback::Capabilities::SCHEDULING);
+    }
+}
+
 int main(int argc, char** argv) {
   ::testing::AddGlobalTestEnvironment(GnssHidlEnvironment::Instance());
   ::testing::InitGoogleTest(&argc, argv);